execute

To orchestrate task dispatch from a plan.json file, use a plan-driven workflow that normalizes inputs, dispatches build tasks to workers, and verifies sub-requirements with gate-capped checks. It treats plan.json as a ledger, ensuring deterministic execution and idempotent resumability.

Contract auto-patching handles interface drift by automatically editing contracts.md when worker outputs indicate mismatches, without requiring user confirmation. It logs every change to audit.md to maintain a deterministic audit trail of the modifications.

To start a plan-driven build workflow, run the orchestration skill in the spec folder containing plan.json or requirements.md. You will be prompted to select a dispatch mode (Direct, Agent, or Team) and a verification depth (Light, Standard, or Thorough).

Yes, you can resume an interrupted task ledger workflow idempotently without polling for completion. The orchestration process skips tasks already marked done in plan.json, enforces dispatch ceilings, and safely restarts from the last recorded state.

For CI-style gate checks, the available dispatch modes are Direct, Agent, and Team, while verification depths include Light, Standard, and Thorough. These options configure gate-capped checks to verify sub-requirements and enforce coverage-driven gap re-dispatch.

You should avoid automated contract verification and task dispatch orchestration when your coding session lacks a structured intent or requirements spec, as the workflow requires a plan.json ledger to safely perform tool-bound mutations and produce an ordered status report.