Use when non-trivial software engineering or an engineering completion claim involves implementation, debugging, refactoring, migration, architecture, technical planning, code review, material assumptions, scope pressure, or unverified evidence. Skip for trivial mechanical edits and pure factual explanation.
Use only when the user explicitly invokes $agent-debate, or when a loaded workflow routes here, and same-topic shared material needs adversarial product tradeoffs, requirement convergence, scope pruning, or decision clarity. Do not use for lanes, returned-lane review, code review, or single-agent brainstorming.
Use only when the user explicitly invokes $agent-eval, or when an active workflow routes here, to convert locked Spec behavior into acceptance evidence, automated/manual checks, failure conditions, fixtures, risk coverage, and implementation evidence requirements before Plan.
Use when the user explicitly invokes $agent-improve or asks what is worth improving in a codebase or branch and wants a read-only ranked audit. Return source-backed findings and stop. Do not use to review a specific artifact or diff (agent-review), implement a known change (steady-coding), or deliver a chosen finding (dev-flow).
Use only when the user explicitly invokes $agent-plan, or when an active workflow routes here, to convert locked Spec and Eval into implementation tasks, coverage matrix, dependencies, files/interfaces, verification commands, evidence expectations, risks, stop conditions, and lane candidates before execution.
Use only when the user explicitly invokes $agent-review, or when a loaded workflow routes here, for one focused reviewer or multiple agents to review the same artifact: Spec, Eval, plan, design, PR, diff, implementation, evidence package, or final result. Do not use for debate, lanes, or returned-lane integration.
Use only when the user explicitly invokes $agent-spec, or when an active workflow routes here, and a governed Requirements Baseline is ready to become implementation behavior before Eval.
Use when the user explicitly invokes $dev-flow, or an already-loaded controller needs development lifecycle routing across multiple gates, resume/handoff state, or unclear ownership. Do not use for ordinary implementation or a single known leaf task.