prd

To generate a PRD from a feature brief, describe your feature idea and answer 3-5 clarifying questions. The tool then outputs a structured PRD with goals, user stories, and acceptance criteria, saving it automatically as a markdown file.

Product requirements documentation should include an introduction, goals, user stories with acceptance criteria, functional requirements, non-goals, and design considerations. Generating these sections ensures alignment and traceability across stakeholders for new features.

Write user stories with acceptance criteria by defining the feature brief and answering targeted clarifying questions. The generated PRD structures these elements to ensure actionable development requirements and clear project scope boundaries.

Yes, you can define non-goals and design considerations when planning a new feature. The generated PRD explicitly includes these sections to establish strict project scope boundaries and guide technical implementation alongside functional requirements.

Vague feature ideas are turned into actionable product requirements by prompting 3-5 essential clarifying questions. This resolves ambiguity and scope upfront, allowing the generation of a comprehensive, structured PRD for stakeholder alignment.

Generated product requirement documents are saved automatically to the tasks directory as markdown files. Specifically, the PRD is stored as tasks/prd-[feature-name].md, ensuring easy reference and versioning for your project planning.