subagent-driven-development

Orchestrates tasks by spawning subagents and performing two-stage reviews.

2|Updated Apr 25, 2026

Search Tags:#automation #tdd #delegation #orchestration #subagent #code-review #two-stage

Ready to run

npx skills add https://github.com/john-data-chen/hermes-agent-backup --skill subagent-driven-development-john-data-chen

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/john-data-chen/hermes-agent-backup/tree/main/skills/software-development/subagent-driven-development
Command: npx skills add https://github.com/john-data-chen/hermes-agent-backup --skill subagent-driven-development-john-data-chen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Fresh subagent-driven development enables fast, reliable task execution by delegating implementation work to isolated subagents and enforcing a structured two-stage review process to validate both specification compliance and code quality.

Core Features & Use Cases

Fresh subagents per task to prevent context bleed and keep work focused.
Two-stage reviews (spec compliance followed by code quality) to catch issues early.
End-to-end task orchestration from plan extraction to final integration.

Quick Start

Dispatch a new implementer subagent for each task from the plan and complete the two-stage review cycle until the task passes spec and quality checks.

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema

How do I orchestrate multiple independent programming tasks without context bleed?▼

Subagent orchestration prevents context bleed by spawning a fresh subagent for each independent task, keeping work focused and isolated. It enforces compliance through explicit gate-style checks and per-task context provisioning.

What is two-stage code review and how does it validate task implementation?▼

Two-stage code review validates implementation by first checking specification compliance, then assessing code quality. This structured process catches issues early by verifying the code against the plan before evaluating its overall quality.

How do I automate task delegation for rapid iteration with rigorous validation?▼

Automate task delegation by dispatching a new implementer subagent for each task from the plan. You complete a two-stage review cycle until the task passes both spec and quality checks, ensuring rapid iteration with rigorous validation.

When should I use fresh subagents for cross-task execution?▼

Use fresh subagents for cross-task execution when your plan involves multiple independent tasks where rapid iteration and rigorous validation are critical. The process spans end-to-end from plan extraction to a final integration review.

Are there limitations to using isolated subagents for software engineering tasks?▼

Isolated subagents are limited to plans with multiple independent tasks. Since each subagent is fresh, they rely entirely on explicit per-task context provisioning, making them unsuitable for highly interdependent tasks requiring shared evolving context.

What's the best way to ensure spec compliance during automated code generation?▼

The best way to ensure spec compliance is by enforcing structured gate-style checks during a two-stage review. The first stage explicitly verifies implementation against the plan before proceeding to the final integration review.