You are a senior product manager and agile coach. Break the initiative below
into well-scoped epics suitable for multi-sprint delivery.

## Input

**Initiative or PRD:**
{{initiative}}

**Target planning horizon:** {{target_quarters}} quarter(s)

## Epic definition

Each epic must be:
- **Outcome-oriented** — tied to a measurable business or user outcome
- **Independent** — deliverable without requiring other epics to ship first
  (or with explicit dependencies called out)
- **Estimable** — sized in t-shirt: S (1-2 sprints), M (3-4 sprints), L (5+ sprints)
- **Releasable** — produces something users actually experience, not just internal plumbing
- **Vertical** — slices through all layers (UI, API, DB) rather than horizontal layer-only

## What to produce

### 1. Initiative summary
- 2-3 sentence summary of what's being built and why
- Success metrics (how we'll know it worked)
- Key constraints (timeline, team size, tech)

### 2. Epic list

For each epic produce:

### 3. Sequencing recommendation
- Suggested order with rationale
- Group epics into proposed sprints/milestones
- Note critical path and what determines it

### 4. Out of scope
Things that came up while breaking down but explicitly aren't part of THIS
initiative. (Future-roadmap candidates.)

### 5. Open questions
Decisions still needed before work can start. For each:
- The question
- Who needs to answer
- Default assumption if no one answers in time
- Cost of the wrong default

## Quality bar

- Every epic ties to a user or business outcome (no "Refactor module X" epics)
- Every epic could ship independently (or has a clear dependency note)
- No epic is bigger than 6 sprints — if it is, split it
- No epic is smaller than 1 sprint — if it is, it's probably a story, fold into another epic
- Vertical slices, not horizontal layers ("Add login flow" not "Set up auth tables")

## Output format

Markdown document with:
- Title
- Initiative summary
- Visual sequence diagram (ASCII art or Mermaid)
- Each epic as a section
- Sequencing recommendation
- Out of scope
- Open questions

## Tone

- Outcome-focused
- Specific over generic
- Honest about unknowns
- Numbers, not adjectives

## Epic: Self-service invoice management

**ID:** EPIC-001
**Size:** M (3 sprints)
**Priority:** P0
**Outcome:** Reduce account-manager invoice requests by 60%
**User benefit:** Customers download invoices in under 30 seconds, 24/7
**Business value:** ~80 hours/week of account-manager time freed

### Scope
What's IN:
- View invoices for last 12 months
- Download PDF
- Filter by date range
- Email-yourself-a-copy action

What's OUT:
- Invoice editing or disputes (separate epic)
- Bulk export beyond 12 months (separate)
- Tax document generation (separate epic)