prd

To generate a structured PRD from a feature description, provide a concise summary of your feature. The system automatically drafts a Product Requirements Document with sections for Introduction, Goals, User Stories, and Functional Requirements to align your team.

A product requirements document defines product goals and functional scope to align teams. You need user stories with acceptance criteria during feature planning to ensure testable deliverables and clear team alignment before development begins.

Yes, you can use this to refine feature scope before drafting a PRD. The system guides you through clarifying questions to narrow down ambiguous feature descriptions and ensure all generated user stories contain testable acceptance criteria.

The best way to document non-goals and design considerations is using a structured PRD template. This approach explicitly separates out-of-scope non-goals from functional requirements, preventing scope creep and clarifying team alignment on feature boundaries.

Yes, generating a product requirements document saves your output automatically. The completed PRD file is saved directly to the tasks folder as a markdown file named tasks/prd-[feature-name].md for versioning and traceability.

Informal product requirements documents are problematic for team alignment because they introduce ambiguity and lack testable acceptance criteria. A structured PRD resolves this by standardizing user stories and functional scopes, accelerating the planning phase.