subagent-driven-development

Orchestrates plan-driven tasks with subagents and two-stage reviews.

31|3|Updated May 7, 2026
One-click install
npx skills add https://github.com/markwang2658/hermes-windows-native --skill subagent-driven-development-markwang2658
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/markwang2658/hermes-windows-native/tree/main/hermes-agent/optional-skills/software-development/subagent-driven-development
Command: npx skills add https://github.com/markwang2658/hermes-windows-native --skill subagent-driven-development-markwang2658

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Fresh subagent per task provides isolated context and focused execution.
  • Two-stage review enforces spec compliance and code quality before proceeding.
  • Plan-driven task orchestration coordinates per-task workflows across implementer, spec reviewer, and quality reviewer.

Quick Start

Define a plan and run the orchestrator to dispatch per-task subagents and sequential 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 orchestrate subagents for task decomposition in software development?

Subagent orchestration dispatches fresh subagents per task to execute decomposed plan steps independently. It coordinates workflows across implementer, spec reviewer, and quality reviewer roles using structured delegation to enforce task isolation.

What is two-stage review in subagent-driven development?

Two-stage review enforces spec compliance and code quality sequentially before proceeding. A spec reviewer validates task requirements while a quality reviewer checks implementation standards, ensuring structured validation loops across delegated subagent tasks.

How do I automate plan-driven workflows with per-task subagent isolation?

Plan-driven automation executes decomposed tasks by dispatching fresh subagents that maintain isolated context. The orchestrator coordinates per-task workflows using delegate_task across implementer and reviewer roles, enforcing must-have checks before advancing.

Can I use subagent orchestration for independent task steps requiring explicit spec validation?

Subagent orchestration applies specifically to plan-driven workflows where tasks are decomposed into independent steps requiring explicit spec and quality validation. It enforces per-task isolation and structured review loops using delegated subagents.

Why use fresh subagents per task instead of persistent agent context?

Fresh subagents per task provide isolated context and focused execution, preventing context bleed across decomposed plan steps. This per-task isolation enforces must-have checks and structured review loops while maintaining execution independence.

Does subagent-driven development require dependencies or external components?

Subagent-driven development operates with no external dependencies or components. It orchestrates end-to-end task delegation using fresh subagents internally, applying two-stage reviews through delegate_task across implementer, spec reviewer, and quality reviewer roles.