Building Workflows

The best workflows are born from successful manual runs, not from wishful thinking.

Start From Success

First, run the task manually in a conversation. Confirm the orchestrator routed it well, the supervisor returned evidence, and the trace looks trustworthy. Then extract that pattern into a workflow.

Step Design

• Make each step responsible for one outcome.
• Avoid putting multiple decisions into one prompt.
• Prefer explicit names over generic step labels.
• Write prompts so a failed step can be diagnosed from its trace.

Run Inspection

After each workflow run, inspect the step output and linked execution trace. A workflow that "usually works" but leaves no evidence trail is not ready to trust.

Workflow Examples

1. Summarize the latest repo activity
2. Inspect the execution trace for failures or unverified results
3. Produce an operator-facing release summary

Next Steps

Continue with Error Handling so your workflows fail honestly instead of hiding weak steps.