Skip to content
Skills Library
Management & product · Automation

lifecycle

/lifecycle

Route Prism work to the host-native story or epic lifecycle and, when explicitly requested, advance a deterministic snapshot of all open Prism epics. Use when the user runs $prism:lifecycle, /prism:lifecycle, or /prism-lifecycle; asks to run or advance the primary host workflow; resumes one host Story or Epic; or asks to process all open Prism epics. Do not use for explicit Prism Callee requests.

Repository
prism ↗
Licence
MIT
Last repository change
22.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Route Prism work to the host-native story or epic lifecycle and, when explicitly requested, advance a deterministic snapshot of all open Prism epics. Use when the user runs $prism:lifecycle, /prism:lifecycle, or /prism-lifecycle; asks to run or advance the primary host workflow; resumes one host Story or Epic; or asks to process all open Prism epics. Do not use for explicit Prism Callee requests.

Original author description

Route Prism work to the host-native story or epic lifecycle and, when explicitly requested, advance a deterministic snapshot of all open Prism epics. Use when the user runs $prism:lifecycle, /prism:lifecycle, or /prism-lifecycle; asks to run or advance the primary host workflow; resumes one host Story or Epic; or asks to process all open Prism epics. Do not use for explicit Prism Callee requests.

How it works

  1. Prerequisites
  2. Resolution priority
  3. Single-item dispatch
  4. Epic batch
  5. Batch outcome
  6. Safety
Original SKILL.md headings · 104 lines, 683 words
SKILL.md preview
---
name: lifecycle
description: >
  Route Prism work to the host-native story or epic lifecycle and, when
  explicitly requested, advance a deterministic snapshot of all open Prism
  epics. Use when the user runs $prism:lifecycle, /prism:lifecycle, or
  /prism-lifecycle; asks to run or advance the primary host workflow; resumes
  one host Story or Epic; or asks to process all open Prism epics. Do not use
  for explicit Prism Callee requests.
---

# Prism lifecycle router

Resolve the user's target, then follow exactly one sibling lifecycle contract:

- full story: [Story skill](../story/SKILL.md)
- epic: [Epic skill](../epic/SKILL.md)

This skill owns target resolution and explicit open-epic batch coordination.
It does not duplicate phase procedure and never invokes Callee. Use the Prism
Callee lifecycle only when the user explicitly requests subagent execution.

## Prerequisites

1. Resolve the Beads workspace with `bd where`; follow the Beads skill or run
   `bd prime` when needed.
2. Require the repository and its native verification tools to be inspectable.
3. Use Beads issue type and parentage as durable routing evidence. Never infer
   item type or lifecycle phase from assignee.

## Resolution priority

Apply the first matching route:

1. An explicit request to process all open Prism epics enters **Epic batch**.
2. An explicit story or epic ID requires that Beads type and dispatches it.
3. An explicit task ID resolves its single parent and requires that parent to
   be a story; then dispatches the parent story.
4. An explicit resume request with no item ID resumes only when exactly one open
   Prism story or epic exists; otherwise ask for the target.
5. Clear initiative intent containing independently deliverable stories creates
   an epic in `prism,phase:epic:frame`, then dispatches it.
6. Ordinary change intent creates a story in `prism,phase:story:specify`, then
   dispatches it.

Never select Light implicitly. Fail closed on a missing item, unsupported Beads
type, missing or ambiguous task parent, nested epic, or direct task under epic.
The selected Story or Epic skill owns phase-label validation. Phase-like labels
outside the supported `phase:story:*` and `phase:epic:*` sets are treated as
absent and are never migrated.

## Single-item dispatch

1. Read the selected item with `bd show <id> --json` and verify its type.
2. For a story, load and follow [Story skill](../story/SKILL.md) in the same host
   invocation.
3. For an epic, load and follow [Epic skill](../epic/SKILL.md) in the same host
   invocation.
4. Preserve every stop condition, approval boundary, write rule, and required
   output of the selected sibling skill.

The router grants no authorization. `human:approved` is item-scoped and may be
written only by the selected lifecycle after unambiguous human approval.

## Epic batch

Enter batch mode only for explicit intent such as "process all open Prism
epics". A generic resume request is not batch intent.

1. Query once at invocation start:

   ```bash
   bd list --label prism --status=open --type=epic --limit 0 --json
   ```

2. Freeze the returned IDs before advancing any item. Sort the snapshot by
   numeric priority ascending, `created_at` ascending, then issue ID ascending.
3. If the snapshot is empty, report that no open Prism epics exist. Create and
   mutate nothing.
4. For each snapshot ID exactly once and sequentially:
   - re-read the epic and record a closed-or-missing race without substituting
     another item;
   - require `issue_type=epic` and label `prism`;
   - load and follow [Epic skill](../epic/SKILL.md) until its normal durable stop;
   - record ending status, supported phase, progress made, gate or blocker, and
     next action;
   - continue to the next snapshot ID after an item-local Human gate, child-story
     gate, blocker, invalid phase, or verification failure.
5. Do not rescan, append newly opened epics, revisit an ID, run items concurrently,
   or transfer `human:approved` between items.
6. Abort the whole batch only when the initial query/snapshot cannot be produced
   safely or Beads becomes unavailable globally.
7. End with one outcome row for every snapshot ID in snapshot order.

## Batch outcome

Use a compact table with these columns:

| Epic | Ending state | Progress | Gate or blocker | Next action |
| --- | --- | --- | --- | --- |

Report item-local failures without claiming the batch succeeded for that item.
The ledger is invocation output, not a second durable lifecycle store.

## Safety

- Beads remains the only durable lifecycle state store.
- Never invent item type, parentage, phase, approval, progress, or outcomes.
- Never invoke `callee agent run prism/...`.
- Never edit `pack/callee/**` while executing a lifecycle.
- Do not implement a story without that story's persisted approval.
- Epic approval never approves its child stories.
- Do not commit or push without repository and user authority.
Files in this package (2)
  • SKILL.md 5 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · baldaworks/prism100MIT
ali-demirbas/claude-lifecycle100MIT
williampsmith/marketing-skills90MIT
Alejo2075/claude-code-aws90MIT
Kiran-980/1ml85MIT

Database snapshot: 13.11.2026 · package version bac4f4384faa (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100prism-lifecycle
    Route Prism work to the host-native story or epic lifecycle and, when explicitly requested, advance a deterministic snapshot of all open Prism epics. Use when the user runs $prism:lifecycle, /prism:lifecycle, or /prism-lifecycle; asks to run or advance the primary host workflow;…
  • 100epic
    Run one host-native Prism epic lifecycle with Beads-backed Frame, Architecture, Roadmap, Approval, Delivery, and Validation phases. Use when the user runs $prism:epic, /prism:epic, /prism-epic, explicitly targets a Prism epic, or asks to continue a multi-story initiative.
  • 90epic
    Epic lifecycle management — create, load, update, and list epics in docs/epics/. TRIGGER when creating a new epic, loading epic context before planning, updating an epic after a session, or listing all epics. SKIP individual feature requirements (use /groom) and roadmap sequencing (use /plan).
  • 95prism
    Use when the user wants to solve or evolve the Prism GPU model-placement benchmark.
  • 84prism-advise
    Get CLAUDE.md recommendations from PRISM. Use when asked to audit, fix, improve, or check what is wrong with a CLAUDE.md file.
  • 84prism-analyze
    Analyze Claude Code session health using PRISM. Use when asked to check token usage, audit CLAUDE.md, understand why sessions are failing, or list projects.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.