shaping-requirements

To shape product requirements, run the workflow to define the problem, set the scope, and assess risks. It guides you through understanding the problem, setting appetite, exploring 2-3 concept shapes, and generating a final pitch.md in the active feature directory.

You define scope and appetite by applying a shaping workflow that iteratively narrows the problem statement and sets boundaries on the solution. This process ensures teams align on the exact problem and constraints before exploring specific concept designs.

You create a product pitch by running the shaping workflow to generate a pitch.md file in your active feature directory. This document captures the finalized problem definition, selected concept shape, and risk assessment to secure team alignment.

Exploring 2-3 conceptual shapes with tradeoffs reduces rework by allowing teams to evaluate different design and engineering decisions upfront. This iterative problem understanding ensures you commit to the most viable solution path before development begins.

Yes, shaping requirements works without external dependencies. It operates standalone to guide teams through problem understanding and risk assessment, requiring only an active feature directory to output the final pitch.md file.