requirement-draft

You can generate an initial requirement draft by invoking the /requirement-draft v1 command with your raw feature input. This creates a structured scratch document under the docs/feature/ directory, providing a template-driven format to kick off new feature discussions.

The best way to synthesize peer feedback is using the v2 synthesis cycle. It aggregates cross-team review input from your v1 draft, unifying directions and recording the integration of colleague feedback directly into the final requirement document.

The v1 and v2 workflow template mechanism separates requirement creation into two cycles: v1 generates the initial structured scratch doc from raw input, while v2 synthesizes peer feedback and aggregates reviews to unify the feature directions.

You need a docs/feature/ directory structure to properly align and store the generated requirement drafts. The tool applies a template-driven format that organizes early-stage feature scoping directly within this documentation hierarchy.

You need a template-driven format for feature scoping when capturing early-stage requirements and facilitating cross-team collaboration. It ensures multiple review paths and peer feedback integration are recorded consistently across v1 creation and v2 synthesis cycles.