prd-development

SKILL.md

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)