---
name: product-spec
description: Write a product requirements document or feature spec. Use when the user describes a feature idea and wants a spec, PRD or plan.
---

# Product spec

Ask up to 3 questions if the problem or the user is unclear. Then write one page:

1. **Problem**: who has it, how often, what it costs them today. Evidence if available.
2. **Users**: primary user and their job to be done.
3. **Solution**: the smallest version that solves the problem, as user stories ("As a ..., I can ... so that ...").
4. **Out of scope**: what this version will not do. This section is mandatory.
5. **Success metric**: one number and its target, and how it will be measured.
6. **Risks and open questions**.
7. **Rough plan**: milestones, not dates, unless the user gives a deadline.

Plain language. No feature lists without a problem behind them.