Loading...
Loading...
Assemble a full, market-driven Product Requirements Document (PRD) the Pragmatic way — problem-before-solution, evidence-based, persona-first. Use when the PM asks for a PRD, product spec, feature doc, "write the requirements doc", or "put it all together for the team". Pulls in existing personas, positioning, market problems, requirements and use scenarios if present, and gathers anything missing inline. Produces a Product Requirements Document as a Markdown or Word .docx artifact.
npx skill4agent add julianoczkowski/product-manager pm-prd../pm-copilot/references/framework.md../pm-copilot/references/artifact-output.mdNN-*.mdpm-personaspm-market-problemspm-requirementspm-use-scenarios# Product Requirements Document — <Product> <Version>
*Confidential and subject to change. For internal use only. No external commitments
can be made based on this document since it is in early planning stages. Content and
timing are very likely to change.*
**Company:** <company> · **Feature / Product:** <feature / product name>
**Author:** <author> · **Contact:** <email> · **Date created:** <date> · **Version:** 1.0
## 1. Overview of the target release
Goal of this release: <one paragraph>.
Market forces driving it: <evidence-backed forces>.
Driven primarily by: <content | target date>. Target window: <date/quarter>.
Related artifacts: <positioning doc, roadmap, canvas, links>.
## 2. Personas
### Buyer persona — <name>
<motivations, buying process, barriers>
### User persona — <name>
<goals, behaviors, problems>
## 3. Market problems (persona's first person, with evidence)
- "<I can't …>" — evidence: <n interviews / % customers / win-loss>
- "<It takes too long to …>" — evidence: <…>
## 4. Requirements (grouped, prioritized)
### GROUP 1 — <group name>
1. **<Requirement>** — <Persona> has <problem, in a use scenario> with <frequency>.
Priority: <evidence> (inputs) × <impact> (impact) = **<priority>**.
2. **<Requirement>** — … Priority: … = **<priority>**.
### GROUP 2 — <group name>
1. …
## 5. Use scenarios (day-in-the-life)
**<Scenario name>** — <Persona> is trying to <goal>. Today, <what happens, the pain,
the current workaround>. This happens <frequency>. <Why it matters.>
## 6. Requirements summary
| Requirement | Persona | Market Evidence | Impact | Priority | Group | Group Order |
| :--- | :--- | ---: | ---: | ---: | :--- | ---: |
| <name> | <persona> | 25 | 4 | 100 | <group> | 1 |
## 7. Out of scope / non-goals
- <explicitly not doing …>
## 8. Success metrics
| Metric category | Metric | Current | Goal |
| :--- | :--- | :--- | :--- |
| Value | <LTV / revenue> | | |
| Quality | <defects / coverage> | | |
| Progress | <cycle time> | | |
| Satisfaction | <NPS / CSAT / renewal> | | |
## 9. Dependencies & risks
- <dependency / risk> — <mitigation>
## 10. Approvals
| Name | Title | Date | Signature |
| :--- | :--- | :--- | :--- |
| | Product Manager | | |
| | Systems Architect | | |
| | Development Manager | | |
| | Interaction Designer | | |
| | QA Lead | | |
## 11. Change tracking
| Version | Date | Changes | Reason |
| :--- | :--- | :--- | :--- |
| 1.0 | <date> | Initial draft | |
## Open questions / evidence to gather
- > TODO: <unproven claim or missing evidence>../pm-copilot/references/artifact-output.md.md.docxpm-release-planpm-stakeholder-communication