Agent Delegation

Supervised external-agent execution through WF-AGENT-DELEGATE-ENTRY and AF-AGENT-DELEGATE.

Overview

Agent delegation hands one bounded task to an external Claude, Codex, or Cursor agent while the parent remains responsible for scope, checkpoints, verification, and the final success claim. It is a supervised execution flow, not an unsupervised replacement for the active workflow.

Host Routes

  • /silver:agent-claude — delegate to Claude Code.
  • /silver:agent-codex — delegate to Codex.
  • /silver:agent-cursor — delegate to Cursor.

The generic catalog entry recognizes agent-delegate, agent-claude, agent-codex, and agent-cursor signals.

Catalog Composition

WF-AGENT-DELEGATE-ENTRY → AF-AGENT-DELEGATE

AF-AGENT-DELEGATE owns the brief, guard activation, host-specific launch and route, checkpoint, verification, relaunch or mentoring when required, and guard teardown.

Supervision Contract

  1. Write a concrete, bounded brief with success evidence.
  2. Activate the delegation guard and launch the selected host route.
  3. Inspect checkpoints and intervene when execution diverges or stalls.
  4. Verify the returned artifacts and claims independently.
  5. Record evidence, then disable the guard.

The flow exits only when every owned flow-step V-loop and the parent flow V-gate pass. The work product is an audited delegation result with an evidence-backed success claim.