prd

To generate a PRD from a feature idea, provide a brief description and the tool outputs a structured document with goals, scope, and acceptance criteria. It uses a self-clarification step to resolve ambiguities automatically.

A standard product requirements document generated here includes Introduction, Goals, Tasks, Functional Requirements, Non-Goals, Technical Considerations, Success Metrics, and Open Questions to formalize planned work.

Document project scope and non-goals by generating a specification that explicitly outlines functional requirements and boundaries. This clarifies what is excluded from the current feature planning cycle.

Yes, the generated specification is automatically saved to specs/prd-[feature-name].md. This ensures reproducible documentation and traceability across design and development teams.

The generator handles ambiguities in a brief feature description using a built-in self-clarification step. It resolves unclear scope and constraints by outlining the problem and success criteria within the PRD.

The best way to formalize acceptance criteria is generating a complete PRD that defines technical considerations and success metrics. This provides a formal plan for validation before development begins.