Execute an existing plan when implementation is authorized and dependent outcomes need tracking; skip short routine checklists.
Mandatory newcomer-safe router for every conversation. Classify by action, impact, and named risk; add workflows only when their descriptions match.
Create a durable plan when explicitly requested, required by the High-risk tier, or needed for resumable dependency coordination; skip routine native planning.
Resolve ambiguous product or system work before implementation. Use when materially different interpretations would change scope, architecture, or consequential outcomes; skip precise tasks.
Complete an authorized commit, push, integration, PR, branch, or worktree action while preserving user state. Use after relevant verification when the user or repository requires delivery.
Evaluate incoming code-review feedback against repository evidence. Keep evaluation-only requests read-only; implement supported fixes only when authorized.
Independently review a defined change before integration when requested or when material security, data, concurrency, migration, contract, or cross-module risk warrants it; exclude incoming feedback.
Diagnose unclear bugs, failing tests, build errors, regressions, or unexpected behavior with evidence. Fix only when implementation is authorized.