Featured

prd

Name: prd
Rating: 5 (2419 reviews)
Author: snarktank

Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature, requirements for, spec out.

TL;DR

Generates structured Product Requirements Documents for new features through clarifying questions and detailed specifications.

What Is It

Creates detailed PRDs for feature planning
Two-step process: questions first, then PRD generation
Saves to tasks/prd-[feature-name].md
Planning tool only - does NOT implement features

Key Features

Asks 3-5 critical clarifying questions with lettered options
Generates structured PRD with 9 standard sections
User stories sized for one focused implementation session
Verifiable acceptance criteria (never vague requirements)
UI stories require 'Verify in browser using dev-browser skill'
All stories include 'Typecheck passes' criterion
Explicit functional requirements (FR-1, FR-2, etc.)
Non-goals section to manage scope boundaries
Written for junior developers and AI agents
Saves to tasks/ directory in markdown format

How to Use

1.User provides feature description or idea
2.Claude asks 3-5 clarifying questions with A/B/C/D options
3.User responds with letter choices (e.g., '1A, 2C, 3B')
4.Claude generates complete PRD with all 9 sections
5.Saves as tasks/prd-[feature-name].md in kebab-case
6.PRD becomes input for implementation or ralph converter

Guardrails & Gotchas

Never start implementing - PRD is planning only
Acceptance criteria must be verifiable, not vague
Always include 'Verify in browser using dev-browser skill' for UI stories
User stories must be small enough for one focused session
Ask only essential questions where prompt is ambiguous
Use lettered options for quick user responses
Functional requirements must be numbered and unambiguous
Non-goals section is critical for scope management

GitHub Stats

Author

@snarktank

Repository

snarktank/ralph

Stars

2419

Explore More Skills

api-design-principles

@wshobson

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers. Use when designing new APIs, reviewing API specifications, or establishing API design standards.

21k

2.3k

2mo ago

prd

Explore More Skills

api-design-principles

revenuecat

create-plan