# Prd Writing

> Write clear Product Requirements Documents (PRDs) that define the problem, goals, scope, requirements, and success criteria for a product or feature. Use when specifying what to build, aligning product/design/engineering, or creating the source of truth for a delivery effort.

- Skill: `itsual/prd-writing` (Agent Skill)
- Install (CLI): `npx skillmds@latest add itsual/prd-writing`
- Raw SKILL.md: https://api.skillmd.com/api/skills/itsual/prd-writing/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: itsual (https://skillmd.com/u/itsual)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/itsual/prd-writing

---


# PRD Writing

## Overview

A good PRD creates shared understanding. It is precise where it needs to be and deliberately open where discovery or design should decide.

## When to Use

- Defining a new feature or product capability
- Aligning cross-functional partners before build
- Handing off requirements to design and engineering
- Documenting decisions for later reference

## Recommended Structure

1. Context and problem statement
2. Goals and non-goals
3. Target users and use cases
4. Success metrics
5. Requirements (functional and non-functional)
6. User experience notes / flows (or links to designs)
7. Edge cases and constraints
8. Open questions and assumptions
9. Launch / rollout considerations
10. Timeline or milestones (if known)

## Principles

- Lead with the problem and outcome, not the solution
- Make non-goals explicit
- Write requirements that are testable
- Keep the PRD living — update it as decisions are made
- Link out to designs, research, and tech specs rather than duplicating them

## Verification

- [ ] Someone new can understand what success looks like
- [ ] Scope boundaries are clear
- [ ] Requirements can be turned into work and tests