subagent-driven-development

Executes implementation plans by dispatching fresh subagents per task with two-stage review.

14|5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill subagent-driven-development-mlt-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/MLT-OSS/hermes-agent-go/tree/main/skills/software-development/subagent-driven-development
Command: npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill subagent-driven-development-mlt-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-task implementation plan in a single session leads to context pollution, inconsistent quality, and missed spec requirements. This Skill orchestrates plan execution by delegating each task to a fresh subagent and enforcing systematic review between tasks. ## Core Features & Use Cases - Per-Task Subagent Dispatch: Sends each plan task to a fresh delegate_task subagent with full context, preventing accumulated state from confusing later work. - Two-Stage Review Pipeline: Runs a spec compliance review first, then a code quality review, with fix-and-re-review loops until each stage passes. - Final Integration Review: After all tasks complete, dispatches a reviewer to verify cross-task consistency, run the full test suite, and confirm merge readiness. - Use Case: Given a plan file like docs/plans/auth-feature.md with five tasks (User model, password hashing, login endpoint, JWT generation, registration endpoint), the Skill creates a todo list, implements each task via TDD-following subagents, reviews each twice, and delivers a fully tested feature. ## Quick Start Execute the implementation plan in docs/plans/feature-plan.md by dispatching a fresh subagent for each task with spec and quality reviews between tasks.

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 subagents?

Read the plan once, extract all tasks into a todo list, then dispatch a fresh implementer subagent per task with the full task text in context. After each implementation, run a spec compliance review followed by a code quality review before marking the task complete.

What is the correct order for spec review and code quality review?

Spec compliance review always comes first, verifying the implementation matches the original task requirements with no scope creep. Code quality review runs only after spec passes, checking conventions, error handling, test coverage, and security issues.

Why use a fresh subagent for each task instead of one session?

Fresh subagents prevent context pollution from accumulated state, giving each task clean, focused context without confusion from prior tasks' code or reasoning. The trade-off is more subagent invocations, but issues are caught earlier and cheaper.

What should I do when a reviewer finds issues in a task?

Have the implementer subagent (or a new fix subagent) address the issues, then re-run the same review until it passes. Never skip the re-review or move to the next task while either review has open critical or important issues.

When should I not use subagent-driven development?

Avoid it when you have no written implementation plan, when tasks are tightly coupled and touch the same files, or when tasks are too large. Each task should be 2-5 minutes of focused work, and parallel dispatch of conflicting tasks is prohibited.