subagent-driven-development

Executes implementation plans by dispatching fresh subagents per task with per-task and final code reviews.

Updated Jan 2, 2025
One-click install
npx skills add https://github.com/mcinnisd/gymbro --skill subagent-driven-development-mcinnisd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/mcinnisd/gymbro/tree/main/.agents/skills/subagent-driven-development
Command: npx skills add https://github.com/mcinnisd/gymbro --skill subagent-driven-development-mcinnisd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Executing a multi-task implementation plan in a single AI session pollutes context, loses progress after compaction, and ships unreviewed code. This Skill orchestrates plan execution through isolated subagents so each task gets fresh context, independent review, and a persistent ledger that survives session interruptions. ## Core Features & Use Cases - Fresh subagent per task: Dispatches an implementer subagent with a task brief file, report file, and explicit model selection, keeping the controller's context clean for coordination. - Two-stage review gates: Runs a task-scoped review (spec compliance plus code quality) after every task and a broad whole-branch review at the end, with a bounded five-round fix loop and adjudication rules. - Ledger-based recovery: Tracks progress in a per-plan workspace ledger and generates review packages via bundled scripts, so work resumes correctly after context compaction. - Use Case: Given a written implementation plan with ten tasks, the controller dispatches implementers one at a time, reviews each diff, loops on findings, and finishes with a final whole-branch review before merging. ## Quick Start Ask the AI to execute your implementation plan using subagent-driven development, pointing it at your plan file so it can dispatch implementer and reviewer subagents per task.

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema
How do I execute an implementation plan with AI subagents?

Dispatch a fresh implementer subagent per task with a task brief file, then run a task review after each and a whole-branch review at the end. Track progress in a ledger file so completed tasks are never re-dispatched after context compaction.

What is the difference between subagent-driven development and executing plans directly?

Subagent-driven development stays in the same session but gives each task a fresh subagent with isolated context, plus a review after every task. Direct plan execution keeps everything in one context, which risks pollution and unreviewed code.

How do I choose which model to use for each subagent task?

Match model capability to task complexity: cheap models for mechanical single-file tasks with complete specs, standard models for multi-file integration, and the most capable model for architecture work and the final whole-branch review. Always specify the model explicitly when dispatching.

What happens when a task review finds problems in the implementation?

Findings enter a fix loop of at most five rounds: rounds one to three resume the original implementer, rounds four and five use a fresh implementer on a more capable model. If findings remain after round five, the controller adjudicates each one and parks or escalates them.

When should I not use subagent-driven development?

Avoid it when there is no written implementation plan, when tasks are tightly coupled and cannot be delegated independently, or when you need a parallel session instead of same-session execution. Brainstorm or plan first in those cases.