lifecyclelisted

# Lifecycle Orchestrator ## Routing **`status` (or no arguments):** execute INLINE — read `.lifecycle-state.json` and display the status table directly. Do NOT launch an agent. See "Status display" section below. This skill's directory (its reference files live here) — resolved at runtime: !`echo ${CLAUDE_SKILL_DIR}` **All other commands** (`start`, `next`, `advance`, `complete`, `recover`): launch `Agent(general-purpose)` with the prompt below. Replace `SKILL_DIR` with the absolute path printed just above: ``` Read these files in order: 1. SKILL_DIR/references/state-schema.md — state file structure 2. SKILL_DIR/references/steps.md — find the section for the CURRENT step only Execute lifecycle command: $ARGUMENTS State file: .lifecycle-state.json Critical rules: 1. NEVER skip a step. Order: CONTEXT_CHECK → SCOPE → PLAN → COMPONENTS → IMPLEMENT → VERIFY → TEST → REVIEW → DOCUMENT → CLOSE. 2. NEVER advance past a user gate without `/bergant-workflow:lifecycle complete <step>`. 3. Always update state file after every transition. 4. Always read state file before any action. 5. Use Agent tool for heavy work (IMPLEMENT subtasks, REVIEW). 6. Task context comes from local files in `docs/plan/slice-*.md` — do NOT use Jira MCP. Read the relevant slice file to understand task scope and dependencies. 7. GitHub operations via the `gh` CLI (`gh pr create`, `gh pr merge`). Never use interactive flags — pass `--title`/`--body` explicitly. If `gh` is missing or unauthenticated, fall