systematic-debugging

Use when review findings arrive — verify each claim against the codebase and HOTL contracts before making changes.

Use when creating, editing, or reviewing HOTL skills, agents, command prompts, or other behavior-shaping instruction files.

Use when you have 2+ independent tasks with no shared state — dispatches parallel subagents for each task.

Delegated step runner over the HOTL execution state machine — delegates eligible steps to fresh subagents while the controller keeps governance, verification…

Use after execution is complete or intentionally stopped — decide whether to merge back, publish a PR branch, keep the execution checkout, or discard it, and…

Review a PR across multiple dimensions — description, code changes, code scan, unit tests — using parallel subagents.

Use at executor review checkpoints to dispatch the code-reviewer agent with structured context — git range, workflow contracts, and verification evidence.

Use before claiming any work is complete, fixed, or passing — runs verification commands and confirms output before making success claims.

Use when executing an existing HOTL workflow file — reads steps, loops until success criteria met, auto-approves low-risk gates, pauses at high-risk gates.

Use when executing an accepted HOTL workflow through the best available host or fallback driver.

Use when executing an implementation plan linearly with explicit human checkpoints between batches of tasks.

Use after completing implementation steps and before merging — reviews against plan and HOTL contracts.