prd-writing

---
name: prd-writing
description: When the user needs to define a product feature, write a product requirements document, or translate an idea into a structured spec.
related: [roadmap-planning, mvp-scoping]
reads: [startup-context]
---

# PRD Writing

## When to Use
Activate when a founder or PM needs to turn a product idea, feature request, or strategic initiative into a structured Product Requirements Document. This includes situations where the user says things like "write a PRD," "spec out this feature," "define requirements for X," or "I need to document what we're building."

## Context Required
- **From startup-context:** company stage, target customer segments, current product state, team size, technical constraints.
- **From the user:** the feature or initiative to spec, known user problems it addresses, any prior research or customer feedback, desired timeline, and scope preference (lightweight vs. full PRD).

## Workflow
1. **Clarify scope level** -- Ask whether this needs a lightweight PRD (early-stage exploration, 2-3 pages) or a full PRD (committed initiative, 5-8 pages). Default to lightweight if the company is pre-product-market-fit.
2. **Gather inputs** -- Collect the problem statement, target users, any existing research, success criteria, and known constraints. Identify key contacts and their roles.
3. **Draft the 8-section PRD** -- Write each section sequentially using the template below. Use accessible language suitable for a broad audience including engineering, design, and leadership.
4. **Flag assumptions** -- Explicitly list key assumptions underlying each section. For each, state what evidence supports it and what would invalidate it.
5. **Review and refine** -- Present the draft, invite feedback, and iterate on specific sections. State the PRD version and last-updated date.

## Output Format
A structured PRD document with 8 sections:… load the full skill through Skill Me