# Product Requirements Doc

Generates a product requirements document for a new feature or project.

- Repository: https://github.com/snarktank/ralph (22106 stars)
- Category: Business
- License: MIT
- Last updated: 2026-02-02
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add snarktank/ralph --skill prd -g -a claude-code -y`
Codex: `npx skills add snarktank/ralph --skill prd -g -a codex -y`
Cursor: `npx skills add snarktank/ralph --skill prd -g -a cursor -y`
Gemini CLI: `npx skills add snarktank/ralph --skill prd -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add snarktank/ralph`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# PRD Generator

Create detailed Product Requirements Documents that are clear, actionable, and suitable for implementation.

---

## The Job

1. Receive a feature description from the user
2. Ask 3-5 essential clarifying questions (with lettered options)
3. Generate a structured PRD based on answers
4. Save to `tasks/prd-[feature-name].md`

**Important:** Do NOT start implementing. Just create the PRD.

---

## Step 1: Clarifying Questions

Ask only critical questions where the initial prompt is ambiguous. Focus on:

- **Problem/Goal:** What problem does this solve?
- **Core Functionality:** What are the key actions?
- **Scope/Boundaries:** What should it NOT do?
- **Success Criteria:** How do we know it's done?

### Format Questions Like This:

```
1. What is the primary goal of this feature?
   A. Improve user onboarding experience
   B. Increase user retention
   C. Reduce support burden
   D. Other: [please specify]

2. Who is the target user?
   A. New users only
   B. Existing users only
   C. All users
   D. Admin users only

3. What is the scope?
   A. Minimal viable version
   B. Full-featured implementation
   C. Just the backend/API
   D. Just the UI
```

This lets users respond with "1A, 2C, 3B" for quick iteration. Remember to indent the options.

---

## Step 2: PRD Structure

Generate the PRD with these sections:

### 1. Introduction/Overview
Brief description of the feature and the problem it solves.

### 2. Goals
Specific, measurable objectives (bullet list).

### 3. User Stories
Each story needs:
- **Title:** Short descriptive name
- **Description:** "As a [user], I want [feature] so that [benefit]"
- **Acceptance Criteria:** Verifiable checklist of what "done" means

Each story should be small enough to implement in one focused session.

**Format:**
```markdown
### US-001: [Title]
**Description:** As a [user], I want [feature] so that [benefit].

The rest: https://github.com/snarktank/ralph/blob/HEAD/skills/prd/SKILL.md