prism-lightlisted

# Prism Light lifecycle | Layer | Owns | | --- | --- | | **Beads** | Story description, acceptance, design, child tasks, status, assignee, labels, comments | | **This skill** | Label-driven phase machine, repository work, and `bd` writes | | **Prism Callee workflow** | Specialized `prism/*` subagents with phase-specific roles and settings; owns all `callee agent run prism/...` execution | **Invoke:** Codex `$prism-light:lifecycle`, Claude Code `/prism-light:lifecycle`, or flat slash `/prism-light`. Lifecycle diagram: [references/lifecycle.md](references/lifecycle.md). Keep lifecycle diagrams vertical with Mermaid `flowchart TB`. ## Durable lifecycle state Exactly one supported story label is the only source of its active lifecycle phase: | Phase | Story label | | --- | --- | | Specify | `phase:story:specify` | | Design | `phase:story:design` | | Breakdown | `phase:story:breakdown` | | Human gate | `phase:story:human` | | Apply | `phase:story:apply` | | Verify | `phase:story:verify` | `prism` marks lifecycle membership. `human:approved` is the only authorization for apply. Story assignees do not encode lifecycle phase state. Ignore phase-like labels outside the supported Story and Epic namespaces as absent and never migrate them. An Epic phase on a story is type-invalid. When no supported global phase exists, initialize `phase:story:specify` without approval. Within the story-level apply phase, child-task assignees record the inner loop: `prism/apply/implementer` then