subagent-driven-development

Dispatch dedicated subagents to implement plan tasks with two-stage review.

Updated May 4, 2026
One-click install
npx skills add https://github.com/Plaidmustache/hermes-nulab --skill subagent-driven-development-plaidmustache
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/Plaidmustache/hermes-nulab/tree/main/skills/software-development/subagent-driven-development
Command: npx skills add https://github.com/Plaidmustache/hermes-nulab --skill subagent-driven-development-plaidmustache

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Dispatching complex implementation plans across specialized subagents with a rigorous two-stage review to ensure compliance and quality, all while maintaining clean context boundaries.

Core Features & Use Cases

  • Fresh subagent per task to prevent context leakage and enable parallel work
  • Two-stage review: spec compliance followed by code quality checks
  • Structured orchestration from plan parsing to completion with automated progress tracking

Quick Start

Dispatch a plan to the subagent-driven workflow and let it execute tasks 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 delegate code implementation tasks to subagents for automated plan execution?▼

To delegate plan execution, this Skill dispatches a fresh subagent per task to implement the work, followed by a two-stage review checking spec compliance and code quality to prevent defects.

What is the best way to automate code review during subagent workflow delegation?▼

Automating code review during subagent delegation requires a two-stage validation process that first checks spec compliance and then enforces code quality checks to maintain standards across independent tasks.

How does using a fresh subagent per task prevent context leakage in automated workflows?▼

Using a fresh subagent per task prevents context leakage by isolating the execution environment for each independent task, which enables parallel work and maintains clean context boundaries throughout the workflow.

When should I use subagent-driven development for TDD and plan execution?▼

You should use subagent-driven development when your plans contain independent tasks, speed and quality are critical, and a structured two-stage review can effectively prevent defects during implementation.

Can I apply subagent delegation to plans with dependent tasks or sequential execution requirements?▼

Subagent delegation is designed for plans with independent tasks where parallel work is possible. It enforces structured per-task delegation and may not suit plans requiring strict sequential task execution.