lifecycle-orchestratorlisted

# Lifecycle Orchestrator ## Purpose The orchestrator is a router and state manager. It does not own phase-specific reasoning. It loads the right phase skill, enforces lifecycle order, writes or updates phase artifacts through those skills, and pauses when user input, evidence, or external action is required. ## Context Loading Always load: 1. Root `AGENTS.md`. 2. `workflow/router.md`. 3. `workflow/lifecycle.md`. 4. `workflow/rules.md`. 5. `workflow/agent-behavior.yaml`. 6. This skill file. 7. These references: - `references/phase-routing.md` - `references/pause-resume-rules.md` - `references/blocker-policy.md` - `references/lifecycle-state-machine.md` - `references/output-schema.md` Load on demand: - `references/exemplar.md` — before finalizing output, to validate paused/advanced/complete state format. - `workflow/config/domain.yaml` when domain rules, terminology, risks, or constraints affect the request. - `workflow/config/repo-profile.yaml` when repo structure, branch policy, public contracts, generated output, or protected paths matter. - `workflow/config/source-of-truth.yaml` when requirements, external tracking, release handoff, or source updates are involved. - `workflow/config/verification.yaml` when planning, testing, reviewing, or shipping verification evidence. - `workflow/config/release.yaml` when release, deployment, publishing, rollback, or handoff is in scope. - `workflow/skills/restore-context/SKILL.md` before resuming an existing slug,