breakdown-feature-prd

To generate a PRD from an epic, provide the epic description and feature context. The system creates a comprehensive document covering goals, personas, user stories, and acceptance criteria, saving it as Markdown to your specified planning directory.

Epic decomposition breaks down large feature descriptions into detailed user stories, functional requirements, and testable acceptance criteria. This process reduces misalignment between product and engineering by documenting explicit out-of-scope items and measurable outcomes early.

Testable acceptance criteria are written by translating feature goals into specific, verifiable conditions. The system automatically generates these criteria alongside functional and non-functional requirements to ensure engineering teams have clear boundaries for each user story.

Yes, you can create a feature PRD with incomplete details. When information is insufficient, the system asks clarifying questions to gather missing context before finalizing the document, ensuring the output remains unambiguous and buildable.

The best way to document non-functional requirements is to include them in a structured PRD. The system generates these alongside functional requirements and out-of-scope boundaries, saving the complete document as a Markdown file for engineering reference.

Generating a PRD saves the output Markdown document to a specific directory path: /docs/ways-of-work/plan/{epic-name}/{feature-name}/prd.md. Ensure your project repository supports this folder structure for proper file storage.