How this skill is triggered — by the user, by Claude, or both
Slash command
/subagent-driven-development:subagent-driven-developmentThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
---
FRESH AGENT = FRESH CONTEXT
Use subagents for focused work without baggage
| Situation | Why Subagent Helps |
|---|---|
| Complex subtask | Focused context, clear scope |
| Going in circles | Fresh perspective breaks loops |
| Parallel work | Multiple things at once |
| Context pollution | Main agent too cluttered |
| Specialized task | Pass only relevant info |
| Research/exploration | Keep main context clean |
The Handoff:
1. DEFINE clear scope - what exactly to do
2. PROVIDE needed context - files, constraints, requirements
3. SPECIFY deliverable - what to return
4. SET success criteria - how to know it's done
Template:
Task: [Specific action to take]
Context:
- Working in [repo/directory]
- Relevant files: [list]
- Constraints: [any limits]
Deliverable:
- [Exact output expected]
Success when:
- [Criteria 1]
- [Criteria 2]
❌ Vague handoffs
Bad: "Look into this bug"
Good: "Find root cause of TypeError in user.ts:45"
❌ Context dumping
Bad: Passing entire conversation history
Good: Passing only relevant files and specific question
❌ No success criteria
Bad: "Make it better"
Good: "Refactor to reduce duplication, all tests must pass"
❌ Too broad scope
Bad: "Implement the whole feature"
Good: "Implement the validation logic for email field"
✅ Research:
✅ Focused fixes:
✅ Generation:
✅ Analysis:
When subagent returns:
1. READ the full response
2. VERIFY against success criteria
3. INTEGRATE results into main context
4. CONTINUE from where you left off
Before launching subagent:
scope-boundary-checker → Is scope clear and bounded?assumption-checker → Are handoff assumptions valid?After receiving results:
fact-checker → Verify subagent claimspre-action-verifier → Before using resultsMain agent responsibilities:
Subagent responsibilities:
npx claudepluginhub a-ariff/ariff-claude-plugins --plugin subagent-driven-developmentGuides creation of specialized Claude Code subagents in .claude/agents/ using TDD process with tasks like RED test, GREEN agent write, and refactor. Use for 'create agent', 'add reviewer', or isolated tasks.
Claude Code subagent lifecycle: creation, configuration, evaluation, and troubleshooting. Invoke whenever task involves any interaction with Claude Code subagents — designing, debugging, iterating, or deciding when to delegate work to isolated agent contexts.
Dispatches subagents for parallel or sequential implementation tasks with a two-stage review cycle (spec compliance, then code quality). Useful when executing multiple independent plan tasks.