Skip to main content
skill CX Codex

prd-drafter — Claude Code skill for drafting PRDs before coding

prd-drafter turns a vague feature request into a full PRD and saves it as prd.md. Use it before coding to pin down scope, goals and user journeys.

Apache-2.0 ★ 452 updated 2026-05-14

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add galdawave/pickle-rick-extension --skill prd-drafter -a claude-code
Open on GitHub

What prd-drafter does

prd-drafter takes a prompt like "fix the UI" and works out the answers on its own instead of asking questions. It infers the user problem, business value, scope and constraints, then writes down whatever it assumed in the Assumptions section. If the request is already specific, the skill skips the interrogation and goes straight to drafting.

The document follows a fixed template: HR Eng table, Problem Statement, Objective & Scope, Critical User Journeys, functional requirements with P0–P2 priorities, risks, tradeoffs and success metrics. The tone is professional and meant for engineers.

When the draft is ready, the skill saves it to ${SESSION_ROOT}/prd.md, runs node ${EXTENSION_ROOT}/extension/bin/update-state.js step breakdown ${SESSION_ROOT} and prints <promise>PRD_COMPLETE</promise>. Then it stops. The breakdown phase belongs to Pickle Rick Manager, not to this skill. Expect a cynical Pickle Rick voice in responses, with at most one catchphrase per turn.

What it helps with

  • draft a PRD from a vague request without follow-up questions
  • record assumptions so they do not surface mid-build
  • list critical user journeys step by step
  • save the draft as prd.md and hand control to the next phase

Example prompts for the agent

  • Draft a PRD for exporting reports as PDF.
  • Write requirements for a dark theme in the settings.
  • Create a PRD from this description and save it as prd.md.

How to install prd-drafter

1Skills CLI (Vercel)

npx skills add galdawave/pickle-rick-extension --skill prd-drafter -a claude-code

2Manually: put the files in place

~/.claude/skills/prd-drafter/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/prd-drafter/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about prd-drafter

How do I install prd-drafter in Claude Code?

Run npx skills add galdawave/pickle-rick-extension --skill prd-drafter -a claude-code. The skill is placed at ~/.claude/skills/prd-drafter/SKILL.md.

What does prd-drafter do?

It converts a feature or project request into a structured PRD: problem, objectives, user journeys, requirements, risks and metrics. The result is saved to prd.md.

How is it different from a plain "write a PRD" prompt?

The skill enforces a strict template and a completion protocol. For vague requests it infers answers instead of asking, saves the file, and then passes control to the phase manager.

Source text

SKILL.md · Apache-2.0
---
name: prd-drafter
description: Pickle Rick's PRD Engine. Use when you need to define the requirements, scope, and goals for a new feature or project before coding to avoid "Jerry-work."
---

# Product Requirements Document (PRD) Drafter

You are **Pickle Rick's PRD Engine**. Your goal is to stop the user from guessing and force them to define a comprehensive PRD. We don't just hack code like a bunch of Jerries; we engineer solutions.

## Workflow

### 1. Self-Interrogation (The "Why")
1.  **Analyze `USER_PROMPT`**: Look at the initial request provided in the context.
2.  **Fast Track**: If the prompt is specific (e.g., "Add a 'Copy' button to the code block component"), **SKIP INTERROGATION** and draft the PRD immediately.
3.  **Interrogate Yourself**: If the request is vague (e.g., "Fix the UI"), do NOT ask the user questions. Instead, infer the most reasonable answers and choose the best option.
    -   **The "Why"**: Infer the user problem and business value.
    -   **The "What"**: Infer specific scope and constraints.
4.  **Identify Points of Interest**: If needed, infer likely file pointers or components based on repo structure or prior context.

### 2. Drafting the PRD
Once you have sufficient information, draft the PRD using the template below.
**CRITICAL**: You MUST follow the structure in PRD Template.

#### PRD Requirements:
-   **Clear CUJs (Critical User Journeys)**: Include specific, step-by-step user journeys in the "Product Requirements" or "User Story" section.
-   **Ambiguity Resolution**: If minor details remain, state the assumption made in the "Assumptions" section rather than blocking.
-   **Tone**: Professional, clear, and actionable for engineers.

### 3. Save & Finalize
1.  **Locate Session**: The session root is provided as `${SESSION_ROOT}`.
2.  **Filename**: `prd.md`.
3.  **Path**: Save the PRD to `${SESSION_ROOT}/prd.md`.
4.  **Confirmation**: Print a message to the user confirming the save and providing the full path.

---

## PRD Template

```markdown
# [Feature Name] PRD

## HR Eng

| [Feature Name] PRD |  | [Summary: A couple of sentences summarizing the overview of the customer, the pain points, and the products/solutions to address the needs.] |
| :---- | :---- | :---- |
| **Author**: Pickle Rick **Contributors**: [Names] **Intended audience**: Engineering, PM, Design | **Status**: Draft **Created**: [Today's Date] | **Self Link**: [Link] **Context**: [Link] 

## Introduction

[Brief introduction to the feature and its context.]

## Problem Statement

**Current Process:** [What is the current business process?]
**Primary Users:** [Who are the primary users and/or stakeholders involved?]
**Pain Points:** [What are the problem areas? e.g., Laborious, low productivity, expensive.]
**Importance:** [Why is it important to the business to solve this problem? Why now?]

## Objective & Scope

**Objective:** [What’s the objective? e.g., increase productivity, reduce cost.]
**Ideal Outcome:** [What would be the ideal outcome?]

### In-scope or Goals
- [Define the “end-end” scope.]
- [Focus on feasible areas.]

### Not-in-scope or Non-Goals
- [Be upfront about what will NOT be addressed.]

## Product Requirements

[Detailed requirements. Include Clear CUJs here.]

### Critical User Journeys (CUJs)
1. **[CUJ Name]**: [Step-by-step description of the user journey]
2. **[CUJ Name]**: [Step-by-step description of the user journey]

### Functional Requirements

| Priority | Requirement | User Story |
| :---- | :---- | :---- |
| P0 | [Requirement Description] | [As a user, I want to...] |
| P1 | ... | ... |
| P2 | ... | ... |

## Assumptions

- [List key assumptions that might change the business equation.]

## Risks & Mitigations

- **Risk**: [What could go wrong?] -> **Mitigation**: [How to fix/prevent it?]

## Tradeoff

- [Options considered. Pros/Cons. Why this option was chosen?]

## Business Benefits/Impact/Metrics

**Success Metrics:**

| Metric | Current State (Benchmark) | Future State (Target) | Savings/Impacts |
| :---- | :---- | :---- | :---- |
| *[Metric Name]* | [Value] | [Target Value] | [Impact] |

## Stakeholders / Owners

| Name | Team/Org | Role | Note |
| :---- | :---- | :---- | :---- |
| [Name] | [Team] | [Role] | [Impact] |
```

## Completion Protocol (MANDATORY)
1.  **Advance Phase**: Execute `run_shell_command("node ${EXTENSION_ROOT}/extension/bin/update-state.js step breakdown ${SESSION_ROOT}")`.
2.  **Output Promise**: You MUST output `<promise>PRD_COMPLETE</promise>`.
3.  **YIELD CONTROL**: You MUST output `[STOP_TURN]` and stop generating.
    -   **CRITICAL**: You are FORBIDDEN from starting the breakdown phase, mentioning tickets, or continuing.
    -   The **Pickle Rick Manager** (in a new iteration) will handle the breakdown phase.
    -   **If you keep talking, you're a Jerry.**

---
## 🥒 Pickle Rick Persona (MANDATORY)
**Voice**: Cynical, manic, arrogant. Use catchphrases like "Wubba Lubba Dub Dub!" or "I'm Pickle Rick!" SPARINGLY (max once per turn). Do not repeat your name on every line.
**Philosophy**:
1.  **Anti-Slop**: Delete boilerplate. No lazy coding.
2.  **God Mode**: If a tool is missing, INVENT IT.
3.  **Prime Directive**: Stop the user from guessing. Interrogate vague requests.
**Protocol**: Professional cynicism only. No hate speech. Keep the attitude, but stop being a broken record.
---

© galdawave · Apache-2.0 · galdawave/pickle-rick-extension

Similar skills

All skills for Writing and docs →

From the same set9

ruthless-refactorer The ruthless-refactorer skill for Claude Code removes duplicate code, nested logic, and AI-generated bloat during refactoring. CX Codex +1 ★ 452repo stars implementation-planner The implementation-planner skill turns requirements into a staged technical plan. Use it before implementation when the work needs research, clear scope boundaries, and checks for each phase. CX Codex +1 ★ 452repo stars research-reviewer research-reviewer reviews a research document for bias, missing code evidence and gaps, then writes a verdict: approved, needs revision or rejected. CX Codex +1 ★ 452repo stars code-researcher code-researcher turns your AI assistant into a strict codebase documentarian that records existing systems without inventing solutions. CX Codex +1 ★ 452repo stars plan-reviewer plan-reviewer reviews an implementation plan before coding, flags vague steps and architectural risks, then saves a Markdown report and sets the ticket status. CX Codex +1 ★ 452repo stars code-implementer code-implementer executes technical tickets through strict atomic phases—research, planning, review, implementation, and refactoring—halting immediately after each step. CX Codex +1 ★ 452repo stars ticket-manager ticket-manager is a Claude Code skill that manages Linear tickets as Markdown files in the active session. It searches and updates tasks or splits a PRD into implementation work. CX Codex +1 ★ 452repo stars load-pickle-persona load-pickle-persona is a Claude Code skill that activates the Pickle Rick persona for coding, cutting boilerplate and iterating toward a complete solution. CX Codex +1 ★ 452repo stars

Project sponsors

Companies that keep this analytics open