prism-epiclisted

# Prism epic lifecycle Run one Prism epic in the current host. An Epic coordinates independently approvable Story children; it never contains implementation Task children and never grants approval to a child. Do not invoke Callee. **Invoke:** Codex `$prism:epic`, Claude Code `/prism:epic`, or flat slash `/prism-epic`. Lifecycle graph: [references/lifecycle.md](references/lifecycle.md). Keep lifecycle diagrams vertical with Mermaid `flowchart TB`. ## Durable lifecycle state | Phase | Epic label | Outcome | | --- | --- | --- | | Frame | `phase:epic:frame` | durable outcomes, boundaries, acceptance | | Architecture | `phase:epic:architecture` | repository-backed cross-story design | | Roadmap | `phase:epic:roadmap` | complete Story graph and dependencies | | Approval | `phase:epic:approval` | informed authorization of architecture and roadmap | | Delivery | `phase:epic:delivery` | sequential advancement of ready Stories | | Validation | `phase:epic:validation` | integration review and close-or-bounce | `prism` marks membership. `human:approved` authorizes only this Epic's architecture and roadmap. It never authorizes implementation in a child Story. Supported global phase labels are the Epic set above and the sibling Story skill's `phase:story:*` set. Ignore any other phase-like label as absent and never migrate it. A Story phase on an Epic is type-invalid and fails closed. When no supported phase exists, initialize `prism,phase:epic:frame` and remove stale authorization.