pm-build-pack-orchestrator

Name: pm-build-pack-orchestrator
Availability: InStock
Author: chenluhan

Coordinate raw feature requests into a Build Pack v1 for engineering handoff.

Updated Apr 15, 2026

Search Tags:#workflow #requirements #handoff #pm #product-management #delta-spec #build-pack

Ready to run

npx skills add https://github.com/chenluhan/skill --skill pm-build-pack-orchestrator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-build-pack-orchestrator
Source: https://github.com/chenluhan/skill/tree/main/.agents/skills/pm-build-pack-orchestrator
Command: npx skills add https://github.com/chenluhan/skill --skill pm-build-pack-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate raw feature requests into a unified Build Pack v1 that can be handed to engineering, preventing scattered notes and incomplete handoffs.

Core Features & Use Cases

Normalize raw briefs into a stable Build Pack
Define problem framing, scope cuts, prototype flow, state matrix, delta spec, and delivery breakdown
Provide a complete Build Pack v1 for engineering handoff with acceptance criteria and open questions

Quick Start

Provide a Build Pack-ready brief from your raw feature request and context.

Frequently Asked Questions about pm-build-pack-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I coordinate raw feature requests into engineering handoff documentation?▼

You normalize raw briefs into a unified Build Pack v1 for engineering handoff. This workflow enforces problem framing, scope cuts, prototype flow, state matrix, delta spec, delivery breakdown, metrics, acceptance, and QA handoff to ensure complete readiness.

What is a Build Pack v1 for product management delivery?▼

A Build Pack v1 is a normalized, ready-to-deliver package for engineering handoff that prevents scattered notes. It defines problem framing, scope cuts, prototype flow, state matrix, delta spec, and delivery breakdown to unify raw feature requests.

How do I normalize a raw product brief into a delta spec and delivery breakdown?▼

You normalize a raw product brief by applying the workflow's structured phases: problem framing, scope cuts, prototype flow, and state matrix. This process outputs a delta spec and delivery breakdown within the final Build Pack v1.

Can I use this workflow for requirement intake and prototype flow framing?▼

Yes, you can use this workflow for requirement intake and prototype flow framing. It is designed for product delivery scenarios including new features, framing, prototypes, and handoff documentation, ensuring all requirements are normalized.

What is the best way to define scope cuts and acceptance criteria for engineering handoff?▼

The best way to define scope cuts and acceptance criteria is to process feature requests through the Build Pack v1 workflow. It systematically enforces scope cuts, state matrix generation, and acceptance criteria definition before QA handoff.

Do I need a complete product brief to start the Build Pack workflow?▼

No, you do not need a complete product brief to start. You provide a Build Pack-ready brief from your raw feature request and context, and the workflow normalizes the raw input into a stable, structured Build Pack v1.