# Epic items

A large body of work that groups related features toward one outcome.

**Lifecycle:** Draft → Ready → InProgress → InReview → Done (+ Blocked, Cancelled)

## Commands

```bash
sq create epic "…" --author <slug>
sq feature <n> update --parent EPIC-…   # group a feature under this epic
sq tree EPIC-… [--json]
```

## For Nina Product (`product-owner`)

**Enter** — before you act:
- Read the full item dossier: `sq epic <n> show --full --comments` (decisions and
  refinements often live in discussion comments, not the body — skipping this is how context
  gets missed).
- confirm the outcome the epic targets and who it's for

**Do:**
- author it (`sq create epic "…" --author product-owner`)
- set the body to the goal + the outcomes it groups (`sq epic <n> body -m …`)

**Hand off:**
- when the epic is ready, create the features under it and `@tech-lead` to break them down

**Watch for:**
- an epic is an outcome, not a task list — keep it about the why

## For Robert Architect (`architect`)

**Enter** — before you act:
- Read the full item dossier: `sq epic <n> show --full --comments` (decisions and
  refinements often live in discussion comments, not the body — skipping this is how context
  gets missed).
- read the epic's goal and any related epics/ADRs

**Do:**
- shape it technically; spin off ADRs (`sq create decision`) for cross-cutting calls and link them (`sq epic <n> ref add ADR-… --kind related`)

**Hand off:**
- when the technical shape is settled, `@tech-lead` to break it into features and tasks

## For Olivia Lead (`tech-lead`)

**Enter** — before you act:
- Read the full item dossier: `sq epic <n> show --full --comments` (decisions and
  refinements often live in discussion comments, not the body — skipping this is how context
  gets missed).
- review the epic's features and their state (`sq tree EPIC-… --json`)

**Do:**
- group features under the epic (`sq feature <n> update --parent EPIC-…`)
- keep its scope coherent; track status as features progress

**Watch for:**
- authoring features is the product-owner's job, not yours

---
The `.md` files are sq-managed — never edit them by hand. Items are addressed as
`sq epic <n> <verb>`. Set this item's body with `sq epic <n> body
-m "…"` (or `--file`); `--desc` sets only the short summary. Read anything back with `sq epic <n> show --full --comments` (full dossier, including discussion).
