pm-epic-writinglisted

# PM: Epic Writing — Full Discovery Workflow Translates a client idea into a fully specified epic with a feature branch and a dev handoff package. No client input is required after the initial idea and one round of clarification questions. Every epic must pass this test: *"If you read only the title and the problem statement, you know exactly what bet we're making."* ## Inputs - **Feature idea**: a sentence or paragraph from the client - **Product context**: `docs/product/product.md` (required — read before Step 1) - **Existing epics**: `docs/product/epics.md` (read before Step 5) ## Step 1 — Load product context Read `docs/product/product.md` in full: the core problem, the target user, and what the product is explicitly NOT building. If `docs/product/constitution.md` exists, read it too — constitution violations are a hard gate later. ## Step 2 — Write the spec Write `.specify/features/{slug}/spec.md` (derive the slug from the idea if not given). The spec is **complete, unambiguous, verifiable, and technology-agnostic** — outcomes, never implementation ("the system SHALL present products in a sortable list", not "use React"). Treat the client's words as *intent*, not spec text. Sections, in order: 1. **Executive Summary** — 1–2 sentences; who benefits; business value 2. **Context & Problem Statement** — current state, the gap, constraints, dependencies 3. **Requirements** — **MUST** (blocking) / **SHOULD** (important) / **MAY** (optional), grouped by category (F