subagent-driven-development

Name: subagent-driven-development
Availability: InStock
Author: huidge

Dispatch fresh subagents per task with two-stage spec and quality reviews.

2|2|Updated Apr 16, 2026

Search Tags:#automation #workflow #planning #delegation #review #subagent #code-review

Ready to run

npx skills add https://github.com/huidge/hermes-skills --skill subagent-driven-development-huidge

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Current development workflows often suffer from context leakage and inconsistent quality when handling large implementation plans. Subagents provide isolated execution contexts per task and enforce a disciplined two-stage review process to catch issues early.

Core Features & Use Cases

Fresh subagent per task to avoid cross-task contamination and maximize parallelism.
Two-stage review: spec compliance followed by code quality review to ensure alignment and maintainability.
Plan-driven execution: integrates with plans created by the writing-plans skill to deliver repeatable results across projects.

Quick Start

Provide an implementation plan and let the system dispatch a fresh subagent for each task, applying two-stage reviews to ensure spec compliance and code quality.

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema

How do I prevent context leakage when executing large implementation plans?▼

To prevent context leakage when executing large implementation plans, dispatch a fresh subagent for each task. This isolates execution contexts and avoids cross-task contamination, ensuring consistent quality and preventing context window overflow.

What is the best way to automate spec compliance and code quality reviews?▼

Automating spec compliance and code quality reviews is best achieved through a two-stage review process. This mechanism enforces spec alignment first, followed by a separate code quality review, catching issues early across development workflows.

How do I orchestrate implementation plans for independent tasks in parallel?▼

Orchestrate implementation plans for parallel execution by dispatching a fresh subagent per task. This per-task delegation maximizes parallelism and provides isolated execution contexts for each independent task within the workflow.

Do I need a pre-defined implementation plan to use subagent delegation?▼

Yes, subagent delegation requires a pre-defined implementation plan. The system integrates with plans created by the writing-plans skill, parsing the plan to dispatch a fresh subagent for each task and deliver repeatable results.

Why does subagent-driven development apply a two-stage review process?▼

Subagent-driven development applies a two-stage review process to enforce disciplined quality control. A spec reviewer ensures alignment with requirements, and a separate quality reviewer checks maintainability, catching issues early before integration.

Can I use subagents for development workflows with dependent tasks?▼

Subagents are suitable for independent tasks where isolated execution contexts are beneficial. For dependent tasks, cross-task contamination prevention remains, but parallelism is limited by the sequential nature of the dependencies.