orchestrating-agentslisted

# Orchestrating development with subagents and workflows Non-trivial development is decomposed and run through the host's subagent and workflow primitives, not done inline. One job: split the work, dispatch fresh-context workers with file briefs, and verify their output independently of whoever produced it. This is also how better-dev builds itself. ## When to reach for this - **Large or many-part** - a migration, building several components, a repo-wide change. - **Parallelizable** - independent slices that don't touch the same files. - **Fresh-context isolation helps** - a broad review or audit that must not inherit your assumptions; a task whose details would otherwise clutter the context you need for coordination. If the task is one small edit you can finish in a few tool calls, do it inline - wrapping it in a brief costs more than the work. Orchestrate when the work outgrows one worker's clean context, or when independence buys correctness. ## Decompose first Break the work into subtasks that are each self-contained: one clear task, enumerated inputs, a deterministic output shape, one obvious approach. If a subtask still needs "investigate," "figure out," or "as appropriate," it isn't decomposed yet - that ambiguity is yours to resolve, not a worker's. Keep the judgment work in your own hands: decomposition, ambiguous design, user interaction, destructive actions, and the final synthesis. Workers get the bounded pieces. (When a judgment stage sits above your sess