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.
Resume an interrupted workflow run with verify-first strategy — loads sidecar state, verifies the last step, and continues execution.
Use when executing an implementation plan linearly with explicit human checkpoints between batches of tasks.
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 record that disposition in HOTL state.
Use when executing an accepted HOTL workflow through the best available host or fallback driver.
Delegated step runner over the HOTL execution state machine — delegates eligible steps to fresh subagents while the controller keeps governance, verification, and stop conditions.
Use when the user explicitly asks for HOTL routing or needs guidance choosing the right HOTL workflow skill.
Use after design approval to create a dated executable workflow file with bite-sized tasks, exact file paths, and loop/gate definitions.