prd

To generate a structured PRD, answer 3-5 clarifying questions about your feature's scope. The PRD is then automatically drafted with Introduction, Goals, User Stories, Acceptance Criteria, and Functional Requirements, saving to tasks/prd-[feature-name].md.

An automatically generated PRD document includes Introduction, Goals, User Stories (US-001 to US-004) with Acceptance Criteria, Functional Requirements, Non-Goals, and optional Design Considerations and metrics sections for comprehensive product planning.

Yes, you can standardize product planning without manual formatting by using PRD automation to guide scope clarification and output a consistent document structure containing goals, user stories, and functional requirements.

You need to answer 3-5 essential clarifying questions before PRD automation begins. This ensures scope clarity so the generated document accurately reflects your feature's goals and functional requirements.

The best way to draft consistent product management documentation is to automate PRD generation. By answering scope questions for each new feature, you produce a standardized artifact saved at tasks/prd-[feature-name].md that can be reused.

Yes, PRD generation includes Non-Goals and optional Design Considerations sections. Defining non-goals explicitly manages scope boundaries, while design considerations capture UI or UX constraints alongside functional requirements.