PDCA cycle: orchestrator contract

The skill is loaded — the task is now driven strictly by the cycle below. Without it the contract does not apply: ordinary tasks are performed directly.

This skill is stack-agnostic and targets software-engineering tasks — writing and changing code, tests, documentation, refactoring, and configuration. The PLAN/CHECK checklists, review lenses and role fallbacks below are generic; for a concrete task, PLAN selects the toolchain and the lenses (§PLAN selects the toolchain and lenses) and the project overlay supplies the concrete commands, thresholds and formats.

Models and providers live outside this skill. The skill names only roles; the host binds them to concrete subagents and models (see §Host requirements below). The design presumption is economy: a cheap orchestrator, cheap scout/coder, medium-tier planner/check/security-auditor, an expensive (strong) escalate used sparingly; if the host gives one model for everything, the cycle still works — just without the cost/quality split.