prd-development
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
npx skills add deanpeters/Product-Manager-Skills --skill prd-development --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Guides product managers through structured PRD creation by orchestrating problem framing, user research synthesis, solution definition, and success criteria into a cohesive document for a major initiative.
How it works
- The skill instructions a PM to draft an Executive Summary, then develop a Problem Statement with who/what/why/evidence, followed by Target Users & Personas, Strategic Context, and a Solution Overview.
- It prescribes associating inputs such as discovery notes, problem framing, and JTBD where relevant, then building sections like Business Goals, Market Opportunity, Competitive Context, and Why Now.
- It specifies writing a high-level Solution Description (2-3 paragraphs) and optionally including user flows, wireframes, or a story map.
- It guides defining Success Metrics: Primary Metric with current vs. target, Secondary Metrics, and Guardrail Metrics.
- It ends with drafting User Stories & Requirements via an Epic Hypothesis process, leveraging a component workflow to generate structured artifacts for engineering handoff.
When to use it
- Use when starting a major feature or product initiative and you need an engineering-ready PRD from discovery notes and research.
- Use to align cross-functional teams on scope, requirements, and success criteria before development begins.
What it can touch
- Tooling and artifacts implied include methods for problem framing, discovery synthesis, and PRD structure (no explicit external touch list provided in this summary).
Caveats
- The description emphasizes that the PRD is a living document capturing strategic context and evolving with delivery, not a pixel-level spec. It does not mandate a fixed contract and encourages ongoing collaboration.
## 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. ## Input **Works best with:** The feature or initiative the PRD covers. **Also useful:** Discovery notes, problem statements, user research, success metrics, and constraints — paste whatever exists; the workflow slots it into the right phases and skips what's already answered. Anything supplied with the invocation itself — text after the skill name, a pasted context dump, or an appended `ARGUMENTS:` line — counts as answers already given. Use it and skip whatever it covers; don't re-ask. **Arriving empty-handed? That works too.** The wo
- Purpose
- Input
- Key Concepts
- What is a PRD?
- PRD Structure (Standard Template)
- Why This Works
- Anti-Patterns (What This Is NOT)
- When to Use This
- When NOT to Use This
- Facilitation Source of Truth
- Application
- Phase 1: Executive Summary (30 minutes)
- Activities
- Phase 2: Problem Statement (60 minutes)
What does the prd-development skill do?
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
How do I install it?
Run `npx skills add deanpeters/Product-Manager-Skills --skill prd-development --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From deanpeters/Product-Manager-Skills, a repository with 6,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.