Simplicity Review

Force the plan toward the least machinery that achieves the requested outcome and covers demonstrated risks. Challenge proposed mechanisms without arguing against the user's desired outcome.

When To Run

• Required for full work.
• Required for fast or tiny work when the plan or adversarial revision adds a material layer, abstraction, dependency, variant, configuration surface, workflow, migration, or coordination mechanism.
• Optional for a lean direct change that only reuses an established path.

Skipping this review must be recorded in the episode state with the route-based reason; it is not silently omitted.

Inputs And Independence

Use a fresh reviewer on the first entry of the plan review role. Pass the brief, revised plan, episode state, complete adversarial findings and dispositions, repository policies, and focused evidence pointers. Do not pass the orchestrator's preferred simplification.

Resolve the reviewer from the plan review role per the kickoff skill's references/config.md, and map the spawn through its references/harness.md. A missing role runs as a fresh child on the parent's model. Never stop to ask the user to configure a reviewer.

The review is read-only. Do not rewrite the plan, implement code, or spawn additional workers. When the harness cannot spawn a child, review inline, label the result non-independent, and record the degraded gate in the episode state.