phase-orchestratorlisted

# Phase Orchestrator ## Goal Run a phase-based plan through a repeatable delegated workflow. The plan is the source of truth, any PRD/spec is supporting context, and each phase should move through orientation, implementation, validation, review, plan updates, and commits by default. Use this skill only when the user explicitly asks for delegated phase orchestration, invokes this skill, or asks to implement a plan/checklist using subagents. ## Companion Skills This skill is the parent of a five-skill workflow: - `write-phase-plan` — authors plans in the format this skill consumes best. - `phase-implementer` — the delegated worker contract for implementing exactly one phase (Phase Loop step 2). - `phase-reviewer` — the delegated worker contract for the review-and-fix pass on a completed phase (Phase Loop step 4). - `phase-final-reviewer` — the delegated worker contract for the end-to-end review of the whole feature after all phases (Final Whole-Feature Pass). Each worker skill carries that role's standing rules: single-phase or single-pass scope, no-revert discipline, no-commit default, and the required final-response format. The parent's prompt only needs to supply the per-run context from the templates below. How to dispatch a worker role depends on the host: 1. **Named custom agents.** If the host supports named custom agents or subagent types (Cursor custom agents, for example), prefer a dedicated agent per role whose definition is the matching companio