Skip to main content
Every recipe below is a complete workflow.md you can copy, validate, and dispatch. Extend any of them with blocks from Snippets; check field meanings in the Workflow Schema.

Choosing a method

The method field selects how a runtime is driven. Rules of thumb: Concretely: research/synthesis → gemini-genai-sdk (sdk); repo implementation → anthropic-agent-sdk (cli or sdk); independent code review → openai-codex-sdk (cli); cheap structured calls → openai-responses-api (api); voice → openai-realtime-api (api) or local-voice; computer use → openai-operator (api); offline/private → local-llm (api).

Recipe: minimal single agent

The smallest valid production workflow — one runtime, fixed route:

Recipe: ordered fallback (resilient single agent)

Try Anthropic first; fall back to Codex, then Antigravity, on failure or credit exhaustion:

Recipe: pair programming (researcher + engineer + reviewer)

Three providers, each where it is strongest, with an isolated reviewer:

Recipe: provider-diverse review panel

Gate completion on a 3-reviewer, cross-vendor consensus:
Add this block to any recipe above; Cadence will not close the run until the panel agrees (any reviewer can block; a block forces rework).

Recipe: state-machine workflow

Multi-stage run where Cadence advances stages only on typed events:
The full worked example combining all of the above is in Workflow Markdown.