subagent-driven-development

Dispatch independent subtasks to parallel subagents using git worktrees.

2|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/iadr-dev/colab --skill subagent-driven-development-iadr-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/iadr-dev/colab/tree/main/skills/subagent-driven-development
Command: npx skills add https://github.com/iadr-dev/colab --skill subagent-driven-development-iadr-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Subagent-driven development prevents slow, conflict-prone single-thread coding by dispatching multiple specialized agents to work on independent parts of a large plan in parallel.

Core Features & Use Cases

  • Parallel subagent dispatch: Runs multiple subagents concurrently when the plan has 3+ independent tasks or exceeds ~2 hours total work.
  • Conflict prevention via git worktrees: Creates isolated branches/worktrees per task to avoid file write conflicts during parallel work.
  • Spec-driven coordination: Stores per-task instructions in .ohc/state/dispatch-{id}.json (including worktree, owned files, and success criteria) so each subagent can operate deterministically.

Quick Start

Dispatch a multi-task plan by creating per-task worktrees, writing task specs to .ohc/state/dispatch-{id}.json, and then running ohc team to execute them in parallel.

Frequently Asked Questions about subagent-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I parallelize coding tasks to speed up large development plans?

Parallelize coding by dispatching independent subtasks to multiple subagents concurrently using git worktrees. This prevents slow, conflict-prone single-thread coding when a plan has three or more independent tasks totaling over two hours.

How does git worktree isolation prevent file write conflicts during parallel development?

Git worktree isolation creates separate branches and working directories for each task. This ensures that multiple subagents operating simultaneously never overwrite the same files, preventing conflicts during parallel code generation.

When should I use subagent-driven development for my build workflow?

Use subagent-driven development during BUILD workflow runs when your multi-task plan contains three or more independent tasks with no dependencies, and the total estimated work time exceeds approximately two hours.

How do I coordinate task instructions for multiple parallel subagents?

Coordinate parallel subagents by writing a per-task JSON dispatch spec to `.ohc/state/dispatch-{id}.json`. This file defines the worktree, owned files, and success criteria so each agent operates deterministically.

What is the best way to verify code merged from parallel git worktrees?

Verify code from parallel worktrees by defining a merge-back strategy that consolidates isolated branches, followed by running a verifier on the merged result to validate the final integrated codebase.

Can I run parallel subagents if my development tasks have dependencies on each other?

No, parallel subagent dispatch requires tasks to be completely independent. If tasks have dependencies on each other, they cannot be safely parallelized using git worktrees and must be executed sequentially.