pm-build-pack-orchestrator

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.

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.

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.

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.

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.

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.