prd

To generate a PRD from a feature idea, provide a feature description and desired goals. The tool outputs a structured document including user stories, acceptance criteria, functional requirements, and success metrics to guide implementation.

Product requirements documentation should include an introduction, goals, user stories with acceptance criteria, functional requirements, non-goals, design considerations, technical considerations, success metrics, and open questions to align teams.

Writing user stories and acceptance criteria is automated by inputting your feature description. The output structures these elements within a comprehensive product requirements document to ensure clear development alignment.

You do not need a detailed prompt to create product requirements. If your input is ambiguous, the tool asks 3-5 essential clarifying questions to gather context before generating the structured document.

The best way to document non-goals and technical considerations is using a structured PRD template. This approach explicitly defines out-of-scope elements and technical constraints alongside functional requirements and success metrics.

Generated product requirements documents are automatically saved as markdown files to a tasks directory. This ensures traceability and future reference by writing the PRD to a structured file path.