PDCA cycle: domain-neutral 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 carried out directly.

The cycle is domain-neutral. It names only roles and phases; it imposes no artefact-specific obligation, no task-type list and no domain example. Whatever the deliverable, PLAN chooses the means and the verification method, and the cycle drives the work to a verifiable result.

Models, providers and tiers live outside this skill. The skill names only roles; the host binds them to concrete subagents and models (§Host requirements). No model id is ever written into a role, this skill or any role prompt — the host profile's agent block binds ids. The design presumption is economy: a cheap orchestrator, cheap execution and fact gathering, medium-tier planning and verdict, a strong escalation role used sparingly.