Build interactive product requirements

Interactively generate Product Requirements Document from clarifying questions

Feature scoping when you need to transform a vague idea into a junior-developer-ready spec through structured clarification.

• · [object Object]
• · [object Object]
• · [object Object]

• · [object Object]
• · [object Object]

• · Write (PRD file)
• · Bash (git add/commit if needed)

Feature scope is understood; user willing to answer clarifying questions; /specs/ directory exists or will be created

• · User prompt is too vague (skips clarifying questions phase)
• · Clarifying questions are leading or assume implementation details
• · PRD requirements are written as user stories (not as "system must" statements)
• · Non-Goals section is missing (scope creep risk)
• · Success metrics are aspirational, not measurable

• · Insists on clarifying questions before PRD (no premature specification)
• · Provides options in letter/number lists (easy response)
• · Requires "I will now create a PRD for X... proceed?" confirmation
• · Requirements are imperative ("The system must..."), not narrative
• · Non-Goals section prevents scope creep
• · Open Questions section documents remaining unknowns