Workflows & agent teams

Some jobs are too big for one Claude working start-to-finish. A workflow splits the work across a *team* of agents that run at the same time — one per file, per module, or per question — and then combines what they found. You describe the goal; the team divides and conquers. Think of it as going from one assistant to a whole room of them.

When one Claude works start-to-finish, you wait for each step in turn. A workflow changes the shape of the work: it splits the job across a team of agents that run at the same time, then gathers their results back into one answer.

The classic shape is fan-out, then gather — give each agent one slice (a file, a page, a question), let them work in parallel, and combine what they find. Some jobs add a verify pass, where a second wave of agents double-checks the first wave’s findings before anything is reported. You describe the goal in plain language; the team divides and conquers.

When a task is genuinely too big for one conversation to coordinate — a codebase-wide audit, a large migration, a research question that needs cross-checking — you can ask for a dynamic workflow. Claude writes an orchestration script for your task and runs it across dozens to hundreds of subagents in the background, verifying the results before it reports back. You manage the runs from /workflows, and the heavy lifting happens while you do something else.

It shines on work that is wide rather than deep: auditing a whole site, applying the same change across dozens of files, or asking one question of many documents. For a single tightly-coupled task, one focused Claude is still the right tool.

create a workflow that migrates every internal fetch() call to the new HttpClient wrapper

Review every page in this site for broken links — run them in parallel and give me one combined report.

/workflows