1. Pick a runtime
Browse Runtimes and choose by capability. For a first workflow,anthropic-agent-sdk (agentic coding) or gemini-genai-sdk
(research/chat) are good defaults — both with method: sdk.
2. Write a minimal workflow
Create aworkflow.md with frontmatter naming your runtime, a budget, tools,
and a sandbox. Keep it declarative — policy, not code:
The
{{workflow_id}} and {{issue_ref}} placeholders are filled by
Cadence at dispatch — you never supply them. See
Template Variables for the full contract,
including how to declare your own typed arguments.3. Validate
Validate the workflow before dispatch — Cadence rejects invalid policy before anything runs (and your editor agent can do this for you via thethink_workflow_md_validate tool).
4. Dispatch through Cadence
Dispatch the workflow from the deeda Think app or via the harness tools. Never bypass Cadence with a raw provider call for production work: budgets, sandboxing, retries, review, and evidence all live on the Cadence path.Next steps
Workflow Markdown
The full schema surface: selection, fallbacks, review consensus, state machines.
Capability Catalog
Everything each provider can do through the harness today.