|
|
@@ -1,13 +1,13 @@
|
|
|
---
|
|
|
name: subagent-driven-development
|
|
|
-description: Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task with code review between tasks, enabling fast iteration with quality gates
|
|
|
+description: Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task with two-stage review (spec compliance then code quality) between tasks
|
|
|
---
|
|
|
|
|
|
# Subagent-Driven Development
|
|
|
|
|
|
-Execute plan by dispatching fresh subagent per task, with code review after each.
|
|
|
+Execute plan by dispatching fresh subagent per task, with two-stage review after each: spec compliance review first, then code quality review.
|
|
|
|
|
|
-**Core principle:** Fresh subagent per task + review between tasks = high quality, fast iteration
|
|
|
+**Core principle:** Fresh subagent per task + two-stage review (spec then quality) = high quality, fast iteration
|
|
|
|
|
|
## When to Use
|
|
|
|
|
|
@@ -32,7 +32,7 @@ digraph when_to_use {
|
|
|
**vs. Executing Plans (parallel session):**
|
|
|
- Same session (no context switch)
|
|
|
- Fresh subagent per task (no context pollution)
|
|
|
-- Code review after each task (catch issues early)
|
|
|
+- Two-stage review after each task: spec compliance first, then code quality
|
|
|
- Faster iteration (no human-in-loop between tasks)
|
|
|
|
|
|
## The Process
|
Jesse Vincent