create-epics

# Create Epics An epic is a named, bounded body of work that maps to one architectural module. It defines **what** needs to be built and **who owns it architecturally**. It does not prescribe implementation steps — that is the job of stories. **Run this skill once per layer** as you approach that layer in development. Do not create Feature layer epics until Core is nearly complete — the design will have changed. **Output:** `production/epics/[epic-slug]/EPIC.md` + `production/epics/index.md` **Next step after each epic:** `/create-stories [epic-slug]` **When to run:** After `/create-control-manifest` and `/architecture-review` pass. --- ## 1. Parse Arguments Resolve the review mode (once, store for all gate spawns this run): 1. If `--review [full|lean|solo]` was passed → use that 2. Else read `production/review-mode.txt` → use that value 3. Else → default to `lean` See `.claude/docs/director-gates.md` for the full check pattern. **Modes:** - `/create-epics all` — process all systems in layer order - `/create-epics layer: foundation` — Foundation layer only - `/create-epics layer: core` — Core layer only - `/create-epics layer: feature` — Feature layer only - `/create-epics layer: presentation` — Presentation layer only - `/create-epics [system-name]` — one specific system - No argument — ask: "Which layer or system would you like to create epics for?" --- ## 2. Load Inputs ### Step 2a — Summary scan (fast) Grep all GDDs for their `## Summary` sections before rea...