lightlisted

Run the simplified Prism Light story lifecycle directly in the host. Beads stores story state, and exactly one phase:* label is the current lifecycle phase. Use when the user runs $prism:light, /prism:light, /prism-light, asks for Prism Light, or explicitly requests the concise host-only lifecycle instead of the full role-aligned workflow.
baldaworks/prism · ★ 9 · AI & Automation · score 77

Install: claude install-skill baldaworks/prism

# 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`, Claude Code `/prism:light`, 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 story label is the only source of its active lifecycle phase: | Phase | Story label | | --- | --- | | Specify | `phase:specify` | | Design | `phase:design` | | Breakdown | `phase:breakdown` | | Human gate | `phase:human` | | Apply | `phase:apply` | | Verify | `phase:verify` | `prism` marks lifecycle membership. `human:approved` is the only authorization for apply. Every open lifecycle story must have exactly one supported `phase:*` label. Story assignees do not encode lifecycle phase state. Within the story-level apply phase, child-task assignees record the inner loop: `prism/apply/implementer` then `prism/apply/reviewer`. Phase references: - Specify: [references/specify.md](references/specify.md) - Design: [references/design.md](references/design.md) - Breakdown: [references/breakdown.md](references/breakdown.md) - Human