plan-create-prd

Generates product-level PRDs through a gated interview covering problem, hypothesis, MVP, and success metrics.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill plan-create-prd-az9713
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-create-prd
Source: https://github.com/az9713/claude-code-hooks-tutorial/tree/main/skills/.claude/skills/plan-create-prd
Command: npx skills add https://github.com/az9713/claude-code-hooks-tutorial --skill plan-create-prd-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump straight into building without a validated problem statement, producing PRDs that are vague, solution-prescriptive, or full of invented requirements. This Skill interviews the user to surface the real problem, evidence, and a falsifiable hypothesis before writing a focused product-level PRD. ## Core Features & Use Cases - Gated interview process: Walks through five phases (initiate, foundation, deep dive, hypothesis, MVP) asking questions in clusters and waiting for answers before proceeding. - Falsifiable hypothesis builder: Co-writes a "We believe..." statement with explicit right and wrong conditions so the bet can be tested. - Structured PRD output: Writes a kebab-slug-named .prd.md file with problem statement, evidence, thesis, hypothesis, JTBD, MVP, success metrics, non-goals, and open questions. - Use Case: A founder with a new product idea runs the skill, answers questions about who has the problem and how they cope today, and receives a PRD with a testable hypothesis and a thin MVP definition, ready to hand off to an architecture spec. ## Quick Start Ask the AI to create a PRD for your product idea, optionally pointing it at research or reference documents to ground the interview in real evidence.

Frequently Asked Questions about plan-create-prd

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

FAQPage Schema
How do I write a PRD for a new product idea?▼

Start with the problem, not the solution: identify who has the pain, how they cope today, and why now. This skill interviews you through gated phases, then writes a PRD with a falsifiable hypothesis, MVP scope, success metrics, and non-goals.

What is the difference between a PRD and an engineering spec?▼

A PRD captures intent: the problem, evidence, hypothesis, users, and success metrics. Engineering decisions like libraries, data models, and project structure belong in a spec, which this skill deliberately defers to a separate architecture step.

Can I generate a PRD without going through an interview?▼

Yes, you can decline the interview and the skill will write the PRD directly. However, anything it could not confirm is marked as "TBD — needs validation" rather than invented, and it will offer the highest-leverage questions first.

What makes a product hypothesis falsifiable?▼

A falsifiable hypothesis states what change you expect, for which users, and includes both a right condition (a leading signal within a timeframe) and a wrong condition (a counter-signal or guardrail). The wrong condition is the most commonly skipped part.

Where does the generated PRD file get saved?▼

The PRD is written to a kebab-case filename derived from the product idea, such as pluggable-ingestion.prd.md, placed in docs/ if it exists or the repo root. If you name a tracker like Jira or Confluence, it writes there instead.