Subagent Driven Development — Execute plans via delegate_task subagents (2-stage review)
Subagent Driven Development — Execute plans via delegate_task subagents (2-stage review)
Start with meaning, then move to detail.
This lesson explains Subagent Driven Development — Execute plans via delegate_task subagents (2-stage review) as part of extending Hermes and connecting external tools. You will learn what it does, when it matters, and the smallest safe test that proves it works.
If you are new, do not memorize names. Focus on three questions: what problem does this solve, what access does it need, and how can you verify the result?
For practice, inspect the first example, identify its effects, run it on test data, and compare the result with the source claim.
For advanced readers, inspect Skill metadata, Reference: full SKILL.md, Overview, then verify failure modes and version compatibility.
Complete installation and one successful task before adding new capabilities.
A clear outcome before you read.
- Understand Subagent Driven Development — Execute plans via delegate_task subagents (2-stage review) without assumed prior knowledge.
- Separate the source description from what still needs testing in your environment.
- Read the first command and identify its inputs and outputs before copying it.
Short definitions before the details.
- Skill
- An instruction bundle that teaches Hermes a repeatable workflow without necessarily adding an external service.
Execute plans via delegate_task subagents (2-stage review)
What does the source say, and in what order?
- 01Skill metadata
Start here to understand the core idea or structure.
- 02Reference: full SKILL.md
Read this after the foundation, then connect it to the previous step.
- 03Overview
Read this after the foundation, then connect it to the previous step.
- 04When to Use
Read this after the foundation, then connect it to the previous step.
- 05The Process
Read this after the foundation, then connect it to the previous step.
- 061. Read and Parse Plan
Read this after the foundation, then connect it to the previous step.
- 072. Per-Task Workflow
Read this after the foundation, then connect it to the previous step.
- 08Step 1: Dispatch Implementer Subagent
Read this after the foundation, then connect it to the previous step.
- 09Step 2: Dispatch Spec Compliance Reviewer
Read this after the foundation, then connect it to the previous step.
- 10Step 3: Dispatch Code Quality Reviewer
Finish here to verify the result and special cases.
Copy only after you understand the effect.
**Key:** Read the plan ONCE. Extract everything. Don't make subagents read the plan file — provide the full task text directly in context.
### 2. Per-Task Workflow
For EACH task in the plan:
#### Step 1: Dispatch Implementer Subagent
Use `delegate_task` with complete context:#### Step 2: Dispatch Spec Compliance Reviewer
After the implementer completes, verify against the original spec:**If spec issues found:** Fix gaps, then re-run spec review. Continue only when spec-compliant.
#### Step 3: Dispatch Code Quality Reviewer
After spec compliance passes:Read the first command and identify its inputs and outputs before copying it.
Match every command to your installed Hermes version, review the files and accounts it can reach, and use non-sensitive data for the first test. If this explanation differs from the source, the official source wins.