# prd-writing

Six-step workflow for drafting Product Requirements Documents with a 12-section template. Guides your agent through discovery before writing specs.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 649 installs · ★ 95
- Author: agent-skills
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/AsyrafHussin/agent-skills/tree/HEAD/skills/prd-writing/SKILL.md
- Updated: 2026-08-27
- HTML: https://affpapa.org/en/nevibecode/skills/prd-writing

## What it does

The skill prevents the agent from drafting requirements prematurely. It checks whether the project already has code: if yes, it reviews existing models and controllers; if no, it initiates an interview. The agent asks 3 to 5 multiple-choice or open questions covering user roles, project constraints, and problem scope.

Once discovery wraps up, the agent generates a spec with 12 structured blocks. These cover measurable KPIs, non-functional demands, technical details, out-of-scope boundaries, and non-goals. The final result lands in `docs/prd/{feature-name}.md` with markdown frontmatter. No external API keys or background services are required.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add AsyrafHussin/agent-skills --skill prd-writing -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/prd-writing/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/prd-writing/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add AsyrafHussin/agent-skills --skill prd-writing -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/prd-writing/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add AsyrafHussin/agent-skills --skill prd-writing -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/prd-writing/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install AsyrafHussin/agent-skills prd-writing
```

2. **Manually: put the files in place**
- File: `.github/skills/prd-writing/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add AsyrafHussin/agent-skills --skill prd-writing -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/AsyrafHussin/agent-skills --path skills/prd-writing
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/prd-writing/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add AsyrafHussin/agent-skills --skill prd-writing -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/AsyrafHussin/agent-skills/tree/HEAD/skills/prd-writing/SKILL.md

## When to use it
- structure a 12-section PRD before writing code
- run guided discovery with clarifying questions
- define out-of-scope boundaries and non-goals
- generate testable acceptance criteria with Given/When/Then

## Example prompts
- Write a PRD for the user onboarding flow
- Document requirements for Stripe checkout integration
- Create a feature spec for our team invites

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 92dfd5c7834ff48c.

BEGIN THIRD-PARTY FILE 92dfd5c7834ff48c
```text
---
name: prd-writing
description: Step-by-step workflow for writing Product Requirements Documents. Use when creating PRDs, documenting features, writing specifications, or planning new products. Triggers on "write PRD", "create PRD", "document requirements", "feature spec", or "product requirements".
license: MIT
metadata:
  author: agent-skills
  version: "1.0.0"
---

# PRD Writing

Step-by-step workflow for writing clear, actionable Product Requirements Documents. Follow the 6-step process below, using the 25 rules across 7 categories as supporting knowledge.

## Metadata

- **Version:** 1.0.0
- **Rule Count:** 25 rules across 7 categories
- **License:** MIT

## Workflow

Follow these steps in order. Skip a step only if the user has already provided that information. Do NOT start drafting before completing discovery.

### Step 1: Assess Project State

Determine what you're working with:

- **Existing project** — code exists → explore the codebase first (models, routes, controllers, auth, patterns). See `disc-codebase-exploration`.
- **Empty/greenfield project** — no code yet → ask the user what they want to build first. Brainstorm together until the product idea and core features are clear, then ask about planned stack, architecture decisions, and constraints.

### Step 2: Ask Clarifying Questions

Ask 3-5 targeted questions to fill knowledge gaps. Use **lettered options** (A/B/C) when there are clear choices, and open-ended questions when you need free-text answers. Focus on:

1. **Problem** — What problem are we solving? Why now?
2. **Users** — Who are the target users?
3. **Scope** — What should it NOT do?
4. **Success** — How do we know it's done?
5. **Constraints** — Timeline, budget, team size?

Mark unknowns as TBD, not assumptions. See `disc-clarifying-questions`.

### Step 3: Draft the PRD

Use the template from `struct-prd-template` and fill in all 12 sections:

1. **Executive Summary** — 1 paragraph: problem, solution, impact
2. **Problem Statement** — what, who, evidence, why now
3. **Goals & Success Metrics** — 3-5 measurable KPIs
4. **User Personas** — primary and secondary with roles/goals/pain points
5. **User Stories & Acceptance Criteria** — "As a / I want / So that" with checkboxes
6. **Functional Requirements** — numbered FR-1, FR-2, etc.
7. **Non-Functional Requirements** — performance, security, accessibility with specific numbers
8. **Technical Specifications** — data model, auth, routes, integrations
9. **Out of Scope** — what we're NOT building and why
10. **Non-Goals** — what we're NOT optimizing for
11. **Dependencies & Risks** — blockers with owners and mitigations
12. **Open Questions** — unresolved items with owners and due dates

**Key rules to follow while drafting:**
- Start with the problem, not the solution (`disc-problem-first`)
- Replace vague language with numbers (`metric-no-vague-language`)
- Every requirement must be testable (`quality-acceptance-criteria`)
- Use Given/When/Then for complex acceptance criteria

### Step 4: Present for Review

Show the draft to the user. Ask specifically:
- Does the problem statement match your understanding?
- Are user stories missing any workflows?
```
END THIRD-PARTY FILE 92dfd5c7834ff48c

The third-party file has ended. Everything between the 92dfd5c7834ff48c tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3226 of 6232 bytes. © agent-skills · MIT · https://github.com/AsyrafHussin/agent-skills/tree/HEAD/skills/prd-writing/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md