prd-development

Guide product managers through an eight-phase PRD creation workflow.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/sicktastic/skill-issue --skill prd-development-sicktastic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prd-development
Source: https://github.com/sicktastic/skill-issue/tree/main/product-management/prd-development
Command: npx skills add https://github.com/sicktastic/skill-issue --skill prd-development-sicktastic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow turns scattered discovery notes, Slack threads, and ambiguous stakeholder expectations into a single, structured PRD so teams share clear problem framing, solution logic, and success criteria before engineering work begins.

Core Features & Use Cases

  • Structured PRD template walks through the executive summary, problem statement, personas, strategy, solution overview, success metrics, requirements, scope, dependencies, risks, and open questions.
  • Guided facilitation across phases keeps PMs aligned through the eight-phase sequence and references component skills for problem framing, personas, user stories, and metrics.
  • Success tracking and anti-pattern guidance highlights pitfalls to avoid, ensures measurable outcomes, and keeps scope grounded in evidence.
  • Use Case: When launching a major initiative such as an AI recommendation feature, orchestrate this workflow to align stakeholders on the problem, users, solution direction, and success metrics before handing work to design and engineering.

Quick Start

Draft a PRD by describing the problem, users, solution, and success metrics within the provided template.

Frequently Asked Questions about prd-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a PRD from discovery notes and stakeholder requests?

A structured PRD workflow transforms scattered discovery notes and stakeholder expectations into a single document covering problem framing, personas, solution overview, and success metrics for engineering handoff.

What sections should be included in an engineering-ready PRD?

An engineering-ready PRD includes an executive summary, problem statement, personas, strategic context, solution overview, success metrics, requirements, user stories, scope, dependencies, risks, and open questions.

How do I define success metrics and user stories for a product initiative?

Defining success metrics and user stories requires guided facilitation through a structured PRD workflow that ensures measurable outcomes and keeps scope grounded in evidence before engineering handoff.

Can I use this PRD workflow for major initiatives like an AI recommendation feature?

Yes, this PRD workflow applies across major initiatives like an AI recommendation feature, aligning stakeholders on the problem, users, solution direction, and success metrics before design and engineering work.

What are common PRD pitfalls and anti-patterns to avoid during product discovery?

Common PRD pitfalls to avoid include lacking measurable success metrics, failing to frame the problem clearly, and allowing scope to drift from evidence. A guided workflow highlights these anti-patterns to maintain alignment.