prd-local

To generate a product requirements document, provide a feature description and answer 3-5 clarifying questions to resolve ambiguity, producing a structured PRD with goals, user stories, and functional requirements.

A PRD for new feature planning should include Introduction, Goals, User Stories, Functional Requirements, and Non-Goals sections to align teams and reduce scope creep.

Yes, you can create a PRD automatically and save it for team handoff by generating the document from a feature prompt, which is saved at tasks/prd-[feature-name].md for traceability.

To turn vague feature ideas into actionable user stories, input the feature prompt and answer clarifying questions, which validates the scope and outputs structured user stories within the PRD.

The best way to document non-goals and prevent scope creep is defining them in a structured PRD, which explicitly lists Non-Goals alongside functional requirements to align team boundaries.

No dependencies are required to write a PRD; the workflow operates standalone, gathering input through clarifying questions and saving the validated document directly to a local markdown file.