prism-lifecyclelisted

# Prism lifecycle router Resolve the user's target, then follow exactly one sibling lifecycle contract: - full story: [Story skill](../prism-story/SKILL.md) - epic: [Epic skill](../prism-epic/SKILL.md) This skill owns target resolution and explicit open-epic batch coordination. It does not duplicate phase procedure and never invokes Callee. Select Prism Light only when the user explicitly invokes `$prism-light:lifecycle`, `/prism-light:lifecycle`, or `/prism-light`. ## 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`, th