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 plan_review.workers.<harness> session. 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.

Use the repository's existing agent-workspace convention and single kickoff.yaml. A selector under plan_review.workers.<harness> contains exactly one of: an exact harness-native agent, or a direct model with optional reasoning_effort when named workers are unsupported. Honor an explicit current choice, validate a saved selector before use, and never substitute a worker silently. If missing, discover available native workers before asking the user to select or configure one, then update only the active harness entry while preserving every other key.

The review is read-only. Do not rewrite the plan, implement code, or spawn additional workers. Under Kickoff, an unavailable independent worker sets the review phase to needs-input or blocked until the user chooses a valid worker or explicitly accepts a non-independent fallback. In standalone use, current-session review is allowed only after the same explicit acceptance and must be labeled non-independent.