subagent-driven-development

Executes implementation plans by dispatching fresh implementer and reviewer subagents per task.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/Yvesdefaria/GymLab --skill subagent-driven-development-yvesdefaria
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/Yvesdefaria/GymLab/tree/main/.opencode/skills/subagent-driven-development
Command: npx skills add https://github.com/Yvesdefaria/GymLab --skill subagent-driven-development-yvesdefaria

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 leads to context pollution, lost progress after compaction, and unreviewed code. This Skill orchestrates plan execution by delegating each task to an isolated subagent with its own review gate, keeping the controller's context clean and every change verified. ## Core Features & Use Cases - Per-task subagent dispatch: Each plan task gets a fresh implementer subagent with a file-based task brief, followed by an independent task reviewer checking spec compliance and code quality. - Bounded fix loop with escalation: Up to five fix rounds per task, resuming the original implementer for rounds 1-3 and escalating to a more capable model for rounds 4-5, with adjudication rulings recorded in a ledger. - Ledger-based recovery: A per-plan workspace with a progress ledger survives context compaction, so completed tasks are never re-dispatched. - Use Case: You have a written implementation plan with eight mostly independent tasks. This Skill creates a git worktree, dispatches implementers and reviewers per task, runs a final whole-branch review, and hands off to branch finishing. ## Quick Start Execute the implementation plan at docs/plans/feature-plan.md using subagent-driven development with per-task reviews.

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 file-based task brief, then dispatch a task reviewer against the diff. Record progress in a ledger file and run a final whole-branch review after all tasks complete.

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

Subagent-driven development stays in the same session but gives each task an isolated subagent context plus a review gate. Direct plan execution uses one continuous context, which risks pollution and unreviewed changes on long plans.

When should I not use subagent-driven development?

Avoid it when tasks are tightly coupled and cannot be implemented independently, or when no implementation plan exists yet. In those cases, brainstorm or plan first, or execute manually with tighter feedback.

How does the fix loop work when a review finds issues?

The controller resumes the original implementer with the findings for rounds 1-3, then dispatches a fresh implementer on a more capable model for rounds 4-5. Each round ends with a scoped re-review; after round 5, remaining findings are adjudicated and recorded as rulings.

Why does subagent-driven development use a ledger file?

The ledger survives context compaction, which in-session memory does not. It records completed tasks, commits, fix rounds, and rulings so a controller that loses its place never re-dispatches finished work.