Structured product requirements document creation using a proven 8-section framework. This skill produces clear, jargon-free PRDs that communicate what to build, why it matters, and how success is measured. Every PRD generated follows a consistent structure that keeps engineering, design, and business stakeholders aligned.
prd_scaffolder.py prints the empty skeleton; the framework and problem framing do the work.Before generating the PRD, settle the inputs below. When one is missing or vague and would change the result, ask about it; when it wouldn't, use a sensible default and say which one you used.
Ask about the two or three inputs that matter most for this request, not the whole list. If the user wants a result straight away, produce it and state your assumptions at the top.
references/prd-framework.md). This is where most of the PRD's value comes from.assets/prd_template.md. Every KR needs a baseline and a target; every P0 item traces back to a stated pain.references/prd-writing-guide.md: an exec gets the Summary in 10 seconds, nothing in Solution lacks a problem above it, and the scope boundary is explicit. Then share for feedback.Optional: the scaffolder prints the empty 8-section skeleton with your name, objective and segments filled in. Writing straight from the template is equally fine.
python3 project-management/execution/create-prd/scripts/prd_scaffolder.py --product-name "SearchBoost" \
--objective "Help shoppers find the right product in under a minute" \
--segments "Power users, New customers" # add --output PRD.md to write a file
Exit codes: 0 skeleton written; 2 missing or empty arguments, or an unwritable --output path.
AI app builders, AI design tools, and AI coding assistants make a clickable or working prototype cheaper than a long spec for some work. Use the prototype to learn; keep the PRD to decide.
Build a prototype first (or alongside the spec) when:
Write the spec first when: the risk is regulatory, data, security, pricing, or cross-team dependency; or the change is a well-understood extension of an existing flow.
Testing the prototype with users:
discovery/brainstorm-experiments/).The PRD still must contain: the problem and who has it (Background), success metrics (Objective KRs), constraints (technical, legal, budget, timeline), explicit non-goals, and risks/open questions. Link the prototype and the test findings in Section 7 (Solution) — the prototype illustrates the solution, it does not replace the requirements.
Handoff to engineering: label the prototype as throwaway or as a starting point, and say which. Generated prototype code is not production code by default — list what it skips (auth, error states, accessibility, performance, security review, data model) so engineering scopes the real build. Hand over the prototype link, the tested flows, the findings, and the P0/P1/P2 scope together.
Mistake: The PRD opens with features, mockups and a P0 list, while Background and Market Segments get one line each.
Why it happens: The team arrives with a solution in mind, and the solution is the part people enjoy writing.
Instead: Write Section 3 (Background) and Section 5 (Market Segments) first. Then test Section 7 alone: if a reader can't tell what problem it solves, the problem sections are still too thin.
Mistake: "Increase activation by 30%", with no current value, no target value and no date.
Why it happens: The baseline needs a data pull, and the PRD is due before anyone runs it.
Instead: Write every key result as "[metric] from [baseline] to [target] by [date]". If the baseline is unknown, measuring it is the first task, not a gap to leave in the document.
Mistake: An Assumptions list with four bullets, none with an owner or a test.
Why it happens: Writing assumptions down feels like managing the risk.
Instead: For each assumption, name who tests it, by when and how. Run the load-bearing ones through discovery/identify-assumptions before build starts.
Nine more, each with a bad and a good example: references/red-flags.md.
references/prd-framework.md — read this while writing: the two pre-PRD techniques, full 8-section framework with per-section guidance, writing principles, scaffolder flag reference, troubleshooting, and success criteria.references/prd-writing-guide.md — read this when polishing a draft: section-by-section writing guide and the review checklist.references/red-flags.md — read this before sharing the PRD: common ways PRDs go wrong with bad/good examples and fixes.| File | Purpose |
|---|---|
scripts/prd_scaffolder.py | Optional skeleton generator |
assets/prd_template.md | Complete PRD template |
examples/shared-dashboards-prd.md | Worked PRD |
In Scope: 8-section PRD skeleton generation with guided placeholders; section-by-section writing guidance (plain-language, specificity); market-segment definition by jobs-to-be-done; value-proposition mapping with Value Curve; release planning with Now/Next/Later and explicit deferral.
Out of Scope: Technical architecture or system design docs (engineering/); user story writing and backlog creation (execution/job-stories/, execution/wwas/); detailed UX research or usability testing plans (product-team/); financial business-case modeling (finance/).
Important Caveats: A PRD is a communication tool, not a contract — treat it as a living document. The 8-section framework is proven, but lightweight agile teams may need only sections 1, 3, 4, 7, 8, while regulated contexts may need more. Unclear or missing requirements are a well-documented source of rework, so review the PRD with engineering and design before build starts.
| Integration | Direction | Description |
|---|---|---|
discovery/identify-assumptions/ | Receives from | Validated and "Test Now" assumptions populate PRD Section 7 with evidence |
discovery/brainstorm-experiments/ | Receives from | Experiment results validate or invalidate PRD assumptions |
discovery/pre-mortem/ | Receives from | Tiger mitigations become PRD risk sections |
execution/brainstorm-okrs/ | Feeds into | PRD Key Results (Section 4) align with quarterly OKR targets |
execution/outcome-roadmap/ | Feeds into | PRD release plan (Section 8) maps to roadmap Now/Next/Later horizons |
execution/prioritization-frameworks/ | Receives from | Feature priority (P0/P1/P2) in Section 7 informed by RICE/ICE scoring |
senior-pm/ | Feeds into | PRD stakeholder context feeds stakeholder mapper engagement plans |