imabusyman/subagent-driven-development
prompts/squad/skills/subagent-driven-development/SKILL.md
Delegate implementation work to specialized subagent instances, each inheriting a task scope and constraints from the parent. Emit structured handoffs, monitor completion signals, aggregate results. Use this in the Orchestrator parallel path when spawning independent Coder/Tester/Infra subagents from a single coordinator.
development
Updated Apr 25, 2026
$ install --global
skillsauthnpx skillsauth add imabusyman/CodebrewRouter subagent-driven-developmentInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 7:21 PM136.4s1 file scanned
SKILL.md
- name:
- subagent-driven-development
- description:
- Delegate implementation work to specialized subagent instances, each inheriting a task scope and constraints from the parent. Emit structured handoffs, monitor completion signals, aggregate results. Use this in the Orchestrator parallel path when spawning independent Coder/Tester/Infra subagents from a single coordinator.
Subagent-Driven Development — hierarchical delegation
Structures multi-agent development as a hierarchy: parent Orchestrator spawns child subagents, each with a bounded scope.
When to use
- A single Orchestrator needs to farm work to multiple Coder subagents (e.g., parallel worktrees).
- Each subagent must be isolated and stateless (no cross-agent chat context).
- Results must be aggregatable back to the parent (clean merge).
Architecture
Orchestrator (parent)
├─ Coder subagent 1 (worktree A, task scope A)
├─ Coder subagent 2 (worktree B, task scope B)
├─ Tester subagent 1 (tests for A + B)
└─ Infra subagent 1 (wire A + B into AppHost)
Each subagent receives:
- Isolated task scope (handoff envelope with exclusive file-lock).
- Read-only artifacts (spec, plan, prior commits).
- Completion signal (emit
[DONE]tag when finished).
Handoff protocol
Parent → subagent:
---
from: orchestrator
to: coder-subagent-1
task: implementation.provider-wiring
files you may edit (exclusive lock):
- Blaze.LlmGateway.Infrastructure/Providers/NewProvider.cs (create)
- .worktrees/add-new-provider/** (working directory)
artifacts to re-read:
- Docs/squad/runs/<ts>/spec.md
- Docs/squad/runs/<ts>/plan.md
inherited assumptions:
- Provider must follow MEAI IChatClient pattern (see CLAUDE.md).
- Quality gate: -warnaserror + 95% coverage.
pending decisions:
- (none)
---
Subagent → parent:
[DONE]
Completed NewProvider.cs + 8 unit tests (100% coverage).
Committed to branch 'feature/add-new-provider'.
Ready for merge.
Aggregation
After all subagents complete [DONE]:
- Quality gate: Merge each subagent's branch, run
-warnaserror+ coverage. - Integrate: Combine all changes into a single coherent state.
- Test end-to-end: Run full test suite on merged main.
- Advance phase: Move to Reviewer or Security-Review.
Best practices
- One subagent per file set (avoid coordination).
- Subagents are stateless (read handoff, work, emit
[DONE], no iterative chat). - Parent tracks progress (collect
[DONE]signals; halt on[BLOCKED]). - Clear ownership (each file belongs to exactly one subagent in a phase).
See also
autonomous-agent-harness— task queue + monitoring for subagents.dispatching-parallel-agents— compute file-disjoint task sets.team-builder— compose subagent teams manually.
Related Skills
imabusyman/write-a-prd
development
VerifiedTrustedCommunity
Generate a Product Requirements Document from a task description, user intent, or PRD outline. Structure the PRD with sections: Overview, Problem Statement, Goals, Scope, Features, Acceptance Criteria, Metrics. Use this when the Planner or Orchestrator needs to formalize requirements before decomposing into implementation steps.
SKILL.mdUpdated Apr 25, 2026
imabusyman/team-builder
development
VerifiedTrustedCommunity
Compose parallel teams of specialized agents for a multi-faceted task. Map subtasks to agent roles, balance workload, and validate team composition. Use this when breaking a task into parallel streams that require different expertise (Coder, Tester, Infra, etc.).
SKILL.mdUpdated Apr 25, 2026
imabusyman/reasoning
testing
VerifiedTrustedCommunity
Maintain the append-only reasoning log and write handoff envelopes for every squad delegation. Use this when the Conductor delegates to a specialist or when a specialist records a non-trivial decision.
SKILL.mdUpdated Apr 25, 2026
imabusyman/quality-gate
development
VerifiedTrustedCommunity
Enforce the -warnaserror build + 95% coverage test gate on every squad [DONE]. Use this before any specialist (Coder, Tester, Reviewer, Infra) marks a phase complete.
SKILL.mdUpdated Apr 25, 2026