What problem does it solve? Non-trivial coding work spanning multiple files or steps loses track of decisions, dependencies, and progress across sessions. This Skill decomposes work into tracked chunks, persists state in a local .orchestration/ markdown store, and coordinates specialist agents so an epic can be paused, resumed, and verified without an external tracker. ## Core Features & Use Cases - Phased state machine: Runs Gate, Intake, Explore, Refine, Design, Decompose, Plan, Execute, Relay, and Converge phases with explicit transition checkpoints and prohibited transitions. - Durable markdown store: Persists PROJECT.md, EPIC.md, and per-issue specs under .orchestration/ with append-only comments, status ownership rules, and resume-from-frontmatter semantics. - Conditional specialist routing: Dispatches repo scouts, planners, reviewers, standards checkers, and WCAG reviewers only when routing predicates match, with per-chunk model selection (haiku through opus) driven by a complexity field. - Use Case: Ask the agent to "track this" refactor across a dozen files; it scouts the repo, decomposes the work into waved issues, dispatches workers with review gates, and resumes exactly where it left off in a later session. ## Quick Start Ask the agent to orchestrate and track the multi-file task you describe, for example by saying "orchestrate this migration and break it down into tracked chunks".
