prd-development
Structured PRD creation from discovery notes to engineering-ready requirements document.
- Orchestrates 8 phases across 2–4 days: problem framing, persona definition, strategic context, solution overview, success metrics, user stories, and scope/dependencies documentation
- Includes problem statement with evidence, target personas, business goals, and competitive context to align stakeholders before engineering begins
- Breaks solutions into epic hypotheses and user stories with acceptance criteria, avoiding vague specs and scope creep
- Explicitly documents out-of-scope items, technical dependencies, risks, and open questions to prevent misalignment during execution
Purpose
Guide product managers through structured PRD (Product Requirements Document) creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohesive document. Use this to move from scattered notes and Slack threads to a clear, comprehensive PRD that aligns stakeholders, provides engineering context, and serves as a source of truth—avoiding ambiguity, scope creep, and the "build what's in my head" trap.
This is not a waterfall spec—it's a living document that captures strategic context, customer problems, proposed solutions, and success criteria, evolving as you learn through delivery.
Key Concepts
What is a PRD?
A PRD (Product Requirements Document) is a structured document that answers:
- What problem are we solving? (Problem statement)
- For whom? (Target users/personas)
- Why now? (Strategic context, business case)
- What are we building? (Solution overview)
- How will we measure success? (Metrics, success criteria)
- What are the requirements? (User stories, acceptance criteria, constraints)
- What are we NOT building? (Out of scope)
More from deanpeters/product-manager-skills
user-story
Create user stories with Mike Cohn format and Gherkin acceptance criteria. Use when turning user needs into development-ready work with clear outcomes and testable conditions.
1.7Kroadmap-planning
Plan a strategic roadmap across prioritization, epic definition, stakeholder alignment, and sequencing. Use when turning strategy into a release plan that teams can execute.
1.5Kcompany-research
Create a company research brief with executive quotes, product strategy, and org context. Use when preparing for interviews, competitive analysis, partnerships, or market-entry work.
1.3Kproduct-strategy-session
Run an end-to-end product strategy session across positioning, discovery, and roadmap planning. Use when a team needs validated direction before committing to execution.
1.2Kprioritization-advisor
Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.
1.1Kuser-story-mapping
Create a user story map that lays out activities, steps, tasks, and release slices. Use when planning a workflow, backlog, or MVP around the user journey.
1.1K