create-prd has an agent write a Product Requirements Document that a team can read in a few minutes: summary, contacts, background, objective, market segments, value propositions, solution and release. It starts from what you provide, asks up to three short questions if the problem, users or success metric are missing, and can research the web. It can also review an existing PRD for gaps and cuts.
What You Get
- A PRD saved as a markdown file named for the product
- Eight sections with an OKR-style objective and one to three key results
- A 6-part JTBD value proposition per segment: who, why, what before, how, what after, alternatives
- A solution section with key features, assumptions and open questions
- A release section covering the first version, later work and what is out of scope
- A short note in the reply on what was skipped on purpose
Common Use Cases
- Writing a first PRD for a new feature
- Reviewing an existing PRD for missing decisions
- Preparing a short spec for engineers and designers
What Makes It Unique
It is lean by default and built around a value proposition for each segment, so the solution delivers the how and the key results measure the what after. It asks for missing problem, user and metric information before writing.
Under The Hood
The skill is one SKILL.md of instructions with no bundled scripts. The agent reads files you provide, may search the web for market and competitor facts and cites them next to the claim, then saves the PRD as a markdown file. It points to the value-proposition skill of a sibling plugin when that is installed.