create-prd

Create-prd guides the authoring of a Product Requirements Document using a fixed eight-section template that covers Summary, Contacts, Background, Objective, Market Segment(s), Value Proposition(s), Solution, and Release. It frames the assistant as an experienced product manager producing an authoritative specification for a named product or feature, with the goal of aligning engineers, designers, leadership, and other stakeholders around a shared understanding of the what, why, and how of an initiative.

Reach for it when writing a new PRD from scratch, documenting product requirements, preparing a feature spec, or reviewing an existing PRD. The workflow starts by gathering information: reading any files the user supplies and using web search when the request references research, URLs, or customer data. Before drafting, it prompts a step-by-step analysis of the problem, the target audience, how success will be measured, and the constraints and assumptions in play. Each section carries specific prompts, for example measuring success with SMART OKR-style key results, defining markets by people's problems and jobs rather than demographics, and describing value through customer jobs, gains, pains avoided, and a Value Curve perspective.

The Solution section is broken into UX and prototypes, key features, optional technology notes, and clearly flagged assumptions, while the Release section favors relative timeframes over exact dates and separates first-version scope from future work. Output is a well-formatted markdown document written in accessible, jargon-free language aimed at a primary-school reading level, and substantial PRDs are saved as PRD-[product-name].md. The skill emphasizes being specific and data-driven, linking each section back to strategy, and flagging assumptions so the team can validate them, and it points to external PRD template references for further reading.