prd-generator

To generate a structured PRD, provide a plain language feature description. The tool asks 3-5 clarifying questions to resolve ambiguity, then outputs a complete PRD with Introduction, Goals, User Stories, Functional Requirements, Non-Goals, and Success Metrics sections.

A standardized product requirements document includes sections for Introduction, Goals, User Stories, Functional Requirements, Non-Goals, and Success Metrics. It also features verification-ready acceptance criteria to ensure completeness for planning workflows.

Yes, you can plan a feature without writing code. The generator enforces a strict non-implementation policy, ensuring the output is strictly a structured plan with specified requirements, not actual source code or technical implementation.

Product requirements documents are automatically saved as markdown files to tasks/prd-[feature-name].md. This auto-saving mechanism ensures easy versioning and straightforward handoff to development teams.

The best way to resolve ambiguity before creating a PRD is answering 3-5 essential clarifying questions generated by the tool. This ensures the final product specification accurately captures goals and functional requirements without missing context.