prd

To generate a PRD, provide a feature prompt describing the desired capability. The tool asks 3-5 clarifying questions with multiple-choice options to resolve ambiguity, then drafts a structured PRD saved to PRD.md.

A product requirements document should include clarifying questions, user stories, acceptance criteria, non-goals, and a progress log. This structure ensures clear goals, scope, and governance to guide development across teams.

You can write user stories and acceptance criteria by inputting a feature prompt. The tool automatically generates these structured elements within the PRD.md file, ensuring formal scope and testable requirements for development.

Yes, you can plan a feature without premature coding. The tool explicitly distinguishes planning tasks from implementation, governing the scope to prevent coding before the product requirements document is fully articulated and approved.

To track progress during feature planning, the tool creates an empty progress.txt file alongside the PRD. You use this log to record incremental work and learnings throughout the project lifecycle.

The PRD generation workflow triggers on phrases like "create a prd", "write prd for", "plan this feature", or "spec out". Providing any of these prompts initiates the clarifying questions and document drafting process.