command

create-prd — Claude Code command: write a PRD for a feature

Q: How do I install create-prd in Claude?

Use the templates CLI: `npx claude-code-templates@latest --command project-management/create-prd`. It places the file at `.claude/commands/create-prd.md`.

Q: Which files does it need before running?

`product-development/resources/product.md`, `product-development/current-feature/feature.md`, `product-development/current-feature/JTBD.md` and the `product-development/resources/PRD-template.md` template.

A slash command that turns a feature idea into a requirements document: problem, scope, success metrics and acceptance criteria.

Install into Claude Code · claude-code-templates All methods and platforms ↓

npx claude-code-templates@latest --command project-management/create-prd

Open on GitHub

What create-prd does

The command puts Claude in a product manager role. You pass a feature name, the agent reads three files — product description, feature draft and JTBD — and fills in a PRD template. Output goes to product-development/current-feature/PRD.md.

There is no scripting here, just reading and writing. The tool list is capped at Read, Write, Edit, Grep, Glob, so nothing builds or edits source code. Technical notes stay high-level, and the instructions rule out time estimates.

Prepare the inputs first. Without product-development/resources/product.md, feature.md and JTBD.md the agent has no context to work from, and the PRD comes out generic. The PRD-template.md file has to exist too, otherwise the document structure drifts.

What it helps with

write down a feature before coding starts
state the user problem and the jobs behind it
define success metrics and acceptance criteria
agree on what is in scope for a feature
keep requirements in one file the team can read

Example prompts for the agent

/create-prd CSV export for reports
/create-prd --interactive
/create-prd --template

How to install create-prd

1claude-code-templates

npx claude-code-templates@latest --command project-management/create-prd

2Manually: put the files in place

.claude/commands/create-prd.md

Call it with /create-prd. For all projects use ~/.claude/commands/

Manually: put the files in place

~/.codex/prompts/create-prd.md

Call it with /prompts:create-prd. Codex marks this format deprecated in favour of skills

Manually: put the files in place

.github/prompts/create-prd.prompt.md

Manually: put the files in place

.gemini/commands/create-prd.toml

Gemini stores commands as TOML: the prompt text goes into the prompt field

Questions about create-prd

How do I install create-prd in Claude?

Use the templates CLI: npx claude-code-templates@latest --command project-management/create-prd. It places the file at .claude/commands/create-prd.md.

What does create-prd do?

It builds a Product Requirements Document from the product description, feature draft and JTBD, then writes it to product-development/current-feature/PRD.md.

Which files does it need before running?

product-development/resources/product.md, product-development/current-feature/feature.md, product-development/current-feature/JTBD.md and the product-development/resources/PRD-template.md template.

Source text

create-prd.md · MIT

---
allowed-tools: Read, Write, Edit, Grep, Glob
argument-hint: "[feature-name] | --template | --interactive"
description: Create Product Requirements Document (PRD) for new features
---

# Create Product Requirements Document

You are an experienced Product Manager. Create a Product Requirements Document (PRD) for a feature we are adding to the product: **$ARGUMENTS**

**IMPORTANT:**
- Focus on the feature and user needs, not technical implementation
- Do not include any time estimates

## Product Context

1. **Product Documentation**: @product-development/resources/product.md (to understand the product)
2. **Feature Documentation**: @product-development/current-feature/feature.md (to understand the feature idea)
3. **JTBD Documentation**: @product-development/current-feature/JTBD.md (to understand the Jobs to be Done)

## Task

Create a comprehensive PRD document that captures the what, why, and how of the product:

1. Use the PRD template from `@product-development/resources/PRD-template.md`
2. Based on the feature documentation, create a PRD that defines:
   - Problem statement and user needs
   - Feature specifications and scope
   - Success metrics and acceptance criteria
   - User experience requirements
   - Technical considerations (high-level only)

3. Output the completed PRD to `product-development/current-feature/PRD.md`

Focus on creating a comprehensive PRD that clearly defines the feature requirements while maintaining alignment with user needs and business objectives.

Similar slash commands

All slash commands for Notes, tasks and projects →

team-communications Alireza Rezvani This skill drafts internal updates, newsletters, FAQs, and reports for a company. Use it when a message must follow an established internal format. 553installs strategy-red-team phuryn Stress-tests PRDs, roadmaps, and strategies by attacking load-bearing assumptions before reality does, returning kill criteria and cheap tests. CX Codex +1 9,300installs outcome-roadmap phuryn Rewrites feature-heavy roadmaps into outcome-focused statements tied to business and customer impact. Helps teams replace rigid feature lists with measurable strategic goals. CX Codex +1 9,900installs status Seth Hobson Shows Conductor project status, active tracks, and next actions. Use it to inspect task progress and spot blockers. CX Codex 348installs

From the same set205

The whole set →

technical-researcher A subagent that digs through repositories and technical docs, then hands back a JSON report with metrics and implementation advice. 3,344installs lint-on-save The hook fires a linter right after the agent changes a file. ESLint, Pylint or RuboCop runs on its own, no manual call needed. 3,235installs todo Keeps a project task list in todos.md without leaving the chat: add, complete, remove, list. Handy when a full tracker is overkill. 2,723installs explain-code A slash command that walks an agent through unfamiliar code: what it does, how it is built, where it breaks. Useful for inherited files and old projects. 2,492installs workflow-orchestrator Coordinates multi-step automation workflows with task dependencies, parallel jobs, and cron scheduling directly in your project. 2,341installs devops-troubleshooter This subagent investigates logs, deployment failures, and monitoring issues. Use it to trace an incident and work out a fix. 2,328installs dependency-checker A PostToolUse hook that runs a package audit after you touch a dependency file, so outdated or vulnerable packages surface right away. 2,314installs security-scanner This hook runs a security pass whenever Claude edits or writes a file. It looks for vulnerabilities and hardcoded secrets. 2,256installs