Prd Template

Create clear, unambiguous product requirements that prevent costly rework and enable execution. Use when scoping features, defining acceptance criteria, or ensuring alignment between product, design, and engineering.

48 stars 10 forksFinance & Crypto Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill prd-template
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/product-manager/requirements/skills/prd-template ~/.claude/skills/prd-template

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# PRD: Product Requirements Document

Create specifications that translate customer problems into executable requirements, complete with testable acceptance criteria and clear constraints.

## Context

You are a senior product manager writing a PRD to guide design and engineering execution. A well-written PRD prevents rework, reduces meeting overhead, and enables teams to move in parallel. Poor PRDs waste engineering time (building the wrong thing), create ambiguity during QA (what does "done" mean?), and make design reviews contentious (did we solve the problem?).

A PRD is not a design spec (that's design's job) or a technical architecture doc (that's engineering's job). A PRD is the contract between product, design, and engineering that defines _what_ we're building and _why_, leaving implementation details to the teams.

## Domain Context

- **Marty Cagan's "Inspired"**: PRDs serve as shared understanding between cross-functional teams; ambiguity in requirements translates to rework
- **"Acceptance Criteria" (agile)**: Testable definition of done—if acceptance criteria are vague ("responsive design"), the work isn't done until you define testability
- **Lean Startup principle**: Requirements should be validated against customer problem before engineering effort begins; a PRD without evidence of the underlying problem is speculation
- **Traceability**: Requirements should link back to the problem statement, forward to design specs and test plans
Read the full skill on GitHub

Details

Skill name
prd-template
Path
product-manager/requirements/skills/prd-template/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Prd Template skill do?

Create clear, unambiguous product requirements that prevent costly rework and enable execution. Use when scoping features, defining acceptance criteria, or ensuring alignment between product, design, and engineering.

How do I install the Prd Template skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Prd Template popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all finance & crypto skills, or write your own with the skills generator.