Subagents
Breaking a flow into planned, delegated steps for tasks that are more than one answer.
Some tasks aren't one question with one answer. They're a sequence of steps that benefit from being planned, delegated, and checked separately. Subagents are how a flow expresses that.
"Implement a ticket" runs as Planner → Implementer → Verifier: a plan gets made, the work gets done in a worktree, and a separate pass checks it before the PR body gets written. Each subagent gets a focused, self-contained brief rather than the whole task at once.
When to add one
- The task has a step that benefits from a different kind of checking, like a dedicated security pass on a PR review.
- Evidence shows a subagent improves outcomes. Verybear surfaces this, like "PRs with the Test gap finder subagent had 31% fewer post-merge fixes."
- The task is long enough that doing it in one pass risks losing track of earlier decisions.
Subagents add cost, so they're not default-on for everything. Fan-out is capped per flow. Verybear will flag flows where more subagents stopped improving results but kept increasing spend.