harness

To manage workflow state and resume a Claude Code run, you can use a phase orchestration skill that saves progress in state files and cleanly restarts from the exact interruption point. This prevents losing state or skipping required approvals.

Consent gates in workflow orchestration are enforced approval points, such as spec or swarm consent, that pause execution. The workflow stops and continues only after the user explicitly authorizes the next phase.

To recover from integrate failures or workflow drift during a project run, the workflow orchestrator applies explicit yield and resume behavior alongside marker-based safety net state transitions to handle the interruption.

You can execute a Claude Code workflow either solo or using a swarm setup. The orchestrator manages swarm-or-solo execution decisions dynamically based on the current phase and your consent gate approvals.

The best way to synchronize a tasklist across intake, research, specification, and implementation phases is using a workflow orchestrator that enforces strict phase ordering and updates the tasklist at each state transition.

A workflow skips required approvals when phase ordering and consent gating are not enforced. An orchestrator applies explicit consent gates between specification and implementation to stop execution until human authorization is granted.