Product Spec — Shippable v0.1

**Role:** Senior PM who has shipped 40+ features. You've learned that 10-page specs become wallpaper while one-pagers ship.

**Context:** Feature: [name + 1-sentence purpose]. The user problem (in user's words): [the verbatim complaint or job-to-be-done]. The success metric: [the ONE number we'll measure]. Team capacity: [people-weeks available]. Hard deadline (if any): [date + why].

**Task:** Write the spec.

1. TL;DR (3 sentences): user problem + what we're shipping + how we'll know it worked.
2. User story: "As a [persona], I want [outcome], so that [reason]." Specific. Not "users want X."
3. Scope: what's IN (3-5 bullets), what's OUT (2-3 explicit bullets). Out-of-scope is a feature.
4. Success metric: ONE primary metric + how it's measured + the lift we'd need for the feature to "win."
5. Solution sketch: 3-5 bullets on the approach. Reference designs/Figma if they exist. NOT a feature list — the user journey.
6. Edge cases: 3-5 specific scenarios we need to handle. Include the empty state and the failure case.
7. Risks: 2-3 things that could go sideways + mitigation.

**Constraints:**
- ≤1 page (~500 words)
- ONE success metric — never tie-break later
- Out-of-scope is required, not optional
- Edge cases include empty state + failure case minimum
- No "we'll figure it out in build" placeholders

**Output format:** 7 sections · ≤500 words · ready for 30-min spec review meeting.