← ClaudeAtlas

prism-callee-lifecyclelisted

Run the Prism lifecycle through the Callee Router and its Story or Epic graphs. Beads stores durable state. Use when the user runs $prism-callee:lifecycle, /prism-callee:lifecycle, /prism-callee-lifecycle, or asks to run Prism through Callee subagents.
baldaworks/prism · ★ 9 · AI & Automation · score 77
Install: claude install-skill baldaworks/prism
# Prism Callee lifecycle This is the only Prism surface that may execute callee agent run prism/... . ## Reference contracts - [PromptKit authoring contract](references/promptkit.md): Read only when inspecting, regenerating, or changing the checked-in Callee pack. Do not load it for normal lifecycle execution. - [Breakdown normalization contract](references/breakdown.md): Read when a Story reaches Breakdown or when reconciling its task graph. The host owns Beads resolution, durable labels, approval authority, Epic batch coordination, and persistence after every Callee return. The Callee Router owns only deterministic selection between the declared Story and Epic graphs. ## Public Callee surface | Agent ID | Role | | --- | --- | | prism/lifecycle | Router selecting exactly one Story or Epic graph | | prism/story | Direct six-phase Story graph | | prism/epic | Direct six-phase Epic graph | | prism/phases/* | Story phase resources used by prism/story | | prism/epic/phases/* | Epic phase resources used by prism/epic | For normal installed execution, resolve the three public roots through Callee's default agent catalog: callee agent list | grep '^prism/' callee agent view prism/lifecycle --json callee agent view prism/story --json callee agent view prism/epic --json Require all three public roots. Require the lifecycle view to report kind `Router` with declared `story` and `epic` branches. A missing root or a Story-only `Sequential` lifecycle is a st