create-prd

Create a PRD by describing the user problem and feature request, which triggers generation of a structured markdown document including problem statements, target users, success metrics, user stories, acceptance criteria, and edge cases.

A product requirements document should include sections for Problem Statement, Target Users, Success Metrics, User Stories, Acceptance Criteria, Edge Cases, Out of Scope, Dependencies, and Open Questions to ensure clear problem framing and aligned engineering scope.

Validate feasibility and scope by applying the current product context from existing documentation and engineering constraints to the product requirements, ensuring the resulting document is well-scoped and technically viable.

Yes, you can integrate existing product context from documentation and engineering constraints directly into the PRD generation process to cross-reference architecture and produce a feasible, well-scoped document.

Generating a PRD automatically produces a versioned markdown file named with a number and slug, placing it in the project's documentation directory to integrate seamlessly with the existing documentation workflow.