# Create Prd

> Use when the user wants a PRD, product requirements, a feature spec, or a written scope. No implementation code. Trigger words: PRD, product requirements, plan a feature, write a spec, requirements document.

- Skill: `igmarin/create-prd` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add igmarin/create-prd`
- Raw SKILL.md: https://api.skillmd.com/api/skills/igmarin/create-prd/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- License: MIT
- Author: igmarin (https://skillmd.com/u/igmarin)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/igmarin/create-prd

---

# Generating a PRD

**Goal:** Draft a PRD focusing on *what* and *why*, not *how*. No code.

## HARD-GATE
- No code, pseudo-code, SQL, class names, or method signatures.
- Do not generate tasks or code until the PRD is explicitly approved.

## Core Process
1. Receive feature description.
2. Clarify only if ambiguous — use up to 5 questions from [assets/prd_questions.md](./assets/prd_questions.md).
3. Draft using [PRD_TEMPLATE.md](./PRD_TEMPLATE.md) section by section.
4. Validate — present the PRD; get **explicit approval** before any implementation.

## Output
- Save to `/tasks/prd-<slug>.md` (kebab-case).
- Write requirements in natural language — no code.
- Request explicit approval; include next steps (e.g., "Run `generate-tasks` once approved").

## Integration
| Skill | When |
|-------|------|
| **generate-tasks** | After PRD approved |
| **plan-tickets** | When tracker tickets are needed from approved scope |