PRD Writer

StrategyIntermediate

Writes Product Requirements Documents (PRDs) using the Socratic method. Generates actionable PRDs covering feature definitions, user stories, success metrics, and technical requirements.

Trigger/prd

FrequencyProject start

PM planning a new feature? Run /prd to cover all bases through structured questioning

Startup founder? Create a clear PRD for the dev team on your own

PRDPlanningProductRequirements

How It Works

Run /prd [feature name] -> start Socratic questions

↓

Phase 1: 4 sections in parallel

problem-def

Define problem

user-story

Generate user stories

spec-write

Write feature spec

metric-set

Set success metrics

↓

Integrate PRD + set priorities

↓

✓ Actionable PRD document

Skill Code

# PRD Writer Skill
## Trigger: /prd [feature name]

When invoked:

1. Start with Socratic questions:
 - What problem does this solve?
 - Who is the target user?
 - What does success look like?
 - What are the constraints?

2. Generate PRD sections:

# PRD: [Feature Name]

## Problem Statement
[What pain point, backed by data if available]

## Goals & Success Metrics
| Metric | Current | Target | Timeline |
|--------|---------|--------|----------|

## User Stories
- As a [persona], I want to [action] so that [benefit]

## Functional Requirements
### P0 (Must Have)
- [ ] [requirement]
### P1 (Should Have)
- [ ] [requirement]
### P2 (Nice to Have)
- [ ] [requirement]

## Technical Requirements
- [API changes, infrastructure, dependencies]

## Design Notes
- [UX considerations, edge cases]

## Timeline
| Phase | Scope | Duration |
|-------|-------|----------|

## Open Questions
- [unresolved decisions]

Copy and paste into your CLAUDE.md to start using immediately.

How PRD Writer Works

PRD Writer conducts a structured interview about your product idea, captures user problems, solution scope, success metrics, and edge cases, then assembles a complete Product Requirements Document with user stories and acceptance criteria.

When to Use PRD Writer

Transforms half-formed product ideas into engineering-ready specifications — invaluable for PMs who need to move fast but still produce thorough documents that engineering teams can implement without ambiguity.

Key Strengths

Structured interview captures requirements systematically
Generates complete PRDs with user stories and acceptance criteria
Identifies edge cases and constraints proactively
Bridges communication gap between product and engineering

Same Category

Strategy View All

Competitor Analysis

Systematically analyzes competitors and generates comparison matrices.

User Story Generator

Generates user stories with acceptance criteria from requirements.

OKR Planning Guide

Guides team/individual OKR creation through a structured process.

Popular in Other Categories

Session Summary

WorkflowAutomatically summarizes changes and next steps at the end of a work session.

Smart Commit

CodingAnalyzes changes and auto-generates meaningful commit messages.

CLAUDE.md Builder

ProductivityAnalyzes your project and auto-generates an optimized CLAUDE.md.