writing-prds

name	writing-prds
description	Use when writing, reviewing, or improving PRDs, product requirements documents, product specs, feature requirements, launch requirements, or product discovery writeups before product or engineering work begins.

Writing PRDs

Write a PRD when the work needs product alignment: what to build, who it is for, why it matters, and how success will be verified.

Rules

• Keep it short and editable.
• Focus on user value and product outcomes, not implementation.
• Mark unknowns as assumptions or open questions.
• Give every meaningful requirement a metric, test, demo path, or launch check.
• If the main question is technical architecture, use writing-rfcs.

Template

# PRD: <feature or product>

## Summary
## User Problem
## Goals / Success Metrics
## Non-goals
## Requirements
## User Flow
## Risks / Assumptions
## Validation Plan
## Open Questions

Check

Before returning it, verify the PRD says why the work matters, what is out of scope, and how the team will know it worked.