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 Infrasity-Labs/dev-gtm-claude-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. Intended for turning scattered notes and Slack threads into a clear, comprehensive PRD that aligns stakeholders, provides engineering context, and serves as a source of truth.
How it works
- Provides a standard PRD structure including executive summary, problem statement, target users, strategic context, solution overview, success metrics, user stories and requirements, out of scope, and risks.
- Defines a phased workflow with activities per phase (Executive Summary, Problem Statement, Target Users & Personas, Strategic Context, Solution Overview, Success Metrics, User Stories & Requirements).
- Specifies inputs and outputs per phase (e.g., Problem Statement with evidence; primary/secondary metrics; personas; business goals; high-level solution description; user stories with acceptance criteria).
- Recommends optional artifacts and tools use (e.g., story maps, user flows, wireframes) to supplement the PRD.
When to use it
Use at the start of a major feature or product initiative to align cross-functional teams on scope and requirements, document decisions for future reference, and onboard new team members to a project.
What it can touch
- References to specific workflow components for problem framing and discovery (e.g., problem framing, discovery inputs, persona documents, story mapping, and Epic/User Story components) to help structure the PRD content.
Caveats
- Describes the PRD as a living document that evolves with learning during delivery.
- Not a detailed UI specification; focuses on problem/solution framing and measurable outcomes, with user stories and acceptance criteria as guidance.
## 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: 1. **What problem are we solving?** (Problem statement) 2. **For whom?** (Target users/personas) 3. **Why now?** (Strategic context, business case) 4. **What are we building?** (Solution overview) 5. **How will we measure success?** (Metrics, success criteria) 6. **What are the requirements?** (User stories, acceptance criteria, constraints) 7. **What are we NOT building?** (Out of scope) ### PRD Structure (Standard Template)
- Purpose
- 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 Protocol
- Application
- Phase 1: Executive Summary (30 minutes)
- Activities
- Phase 2: Problem Statement (60 minutes)
- Outputs from Phase 2
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 Infrasity-Labs/dev-gtm-claude-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 Infrasity-Labs/dev-gtm-claude-skills, a repository with 97 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.