prd

To write a Product Requirements Document, you need to provide an explicit feature description, triggers, and success criteria. The system then asks clarifying questions to define scope and generates a structured PRD with goals, user stories, and metrics.

A PRD for product planning should include sections for Goals, User Stories, Functional Requirements, Non-Goals, and Metrics. Generating these defined sections ensures team alignment and reduces ambiguity in feature development.

You define success criteria and scope for feature development by answering interactive clarifying questions about your feature description and triggers. This process captures the exact requirements needed to align engineering teams and guide the project.

Yes, the generated PRD auto-saves directly to a markdown file named tasks/prd-[feature-name].md. This allows for easy tracking and documentation management within your existing project repository.

No technical dependencies are required to generate product specifications with this tool. You simply need to provide the feature description and triggers to start the interactive process of building your structured PRD outline.

The best way to structure product specifications for engineering teams is to use an interactive system that defines goals, functional requirements, and non-goals. This approach ensures actionable documentation that guides development and reduces planning ambiguity.