Subagent Driven Development

Use when: orchestrate specialized subagents to handle distinct parts of one larger task.

kimtth 25fec95 1.1 KB Updated

File contents

Goal: coordinate focused subagents so each does one job well.

Use for:

  • tasks with separable concerns (research, implement, test, review)
  • work too large for a single context to hold cleanly
  • parallelizable streams that need a coordinator

Workflow:

  1. Decompose the task into independent, well-scoped units.
  2. For each unit, write a self-contained brief and success criteria.
  3. State exactly what each subagent must return.
  4. Dispatch read-only or independent units in parallel.
  5. Integrate results; resolve conflicts and gaps yourself.
  6. Verify the combined outcome against the original goal.

Briefs include:

  • objective and constraints
  • inputs and relevant files
  • required output format
  • what is out of scope

Rules:

  • one clear responsibility per subagent
  • never assume a subagent shares your context; spell it out
  • keep write operations on one unit to avoid collisions
  • the orchestrator owns final verification

kimtth/agent-skill-100-lines-or-less/tree/main/skills/subagent-driven-development commit 25fec95681

Frequently asked questions

npx skillmds@latest add kimtth/subagent-driven-development