industrial/_project-template/skill-subagent-driven-development

Claude Code and agent skill by industrial/_project-template

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

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

Install

npx vskill@latest install industrial/_project-template/skill-subagent-driven-development

SKILL.md

The same SKILL.md was published earlier as industrial/_project-template/skill-subagent-driven-development.

Subagent-Driven Development

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

Overview

  • 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)
  • Faster iteration (no human-in-loop between tasks)
  • When to use:
  • Staying in this session
  • Tasks are mostly independent
  • Want continuous progress with quality gates
  • When NOT to use:
  • Need to review plan first (use executing-plans)
  • Tasks are tightly coupled (manual execution better)
  • Plan needs revision (brainstorm first)

The Process

✅ Good: 2. Execute Task with Subagent
Task tool (general-purpose):
description: "Implement Task N: [task name]"
prompt: |
You are implementing Task N from [plan-file].
Read that task carefully. Your job is to:
1. Implement exactly what the task specifies
2. Write tests (following TDD if task says to)
3. Verify implementation works
4. Commit your work
5. Report back
Work from: [directory]
Report: What you implemented, what you tested, test results, files changed, any issues
✅ Good: 3. Review Subagent's Work
Task tool (superpowers:code-reviewer):
Use template at requesting-code-review/code-reviewer.md
WHAT_WAS_IMPLEMENTED: [from subagent's report]
PLAN_OR_REQUIREMENTS: Task N from [plan-file]
BASE_SHA: [commit before task]
HEAD_SHA: [current commit]
DESCRIPTION: [task summary]
✅ Good: 4. Apply Review Feedback
"Fix issues from code review: [list issues]"

Example Workflow

✅ Good: ```
You: I'm using Subagent-Driven Development to execute this plan.
[Load plan, create TodoWrite]
Task 1: Hook installation script
[Dispatch implementation subagent]
Subagent: Implemented install-hook with tests, 5/5 passing
[Get git SHAs, dispatch code-reviewer]
Reviewer: Strengths: Good test coverage. Issues: None. Ready.
[Mark Task 1 complete]
Task 2: Recovery modes
[Dispatch implementation subagent]
Subagent: Added verify/repair, 8/8 tests passing
[Dispatch code-reviewer]
Reviewer: Strengths: Solid. Issues (Important): Missing progress reporting
[Dispatch fix subagent]
Fix subagent: Added progress every 100 conversations
[Verify fix, mark Task 2 complete]
...
[After all tasks]
[Dispatch final code-reviewer]
Final reviewer: All requirements met, ready to merge
Done!

Advantages

  • vs. Manual execution:
  • Subagents follow TDD naturally
  • Fresh context per task (no confusion)
  • Parallel-safe (subagents don't interfere)
  • vs. Executing Plans:
  • Same session (no handoff)
  • Continuous progress (no waiting)
  • Review checkpoints automatic
  • Cost:
  • More subagent invocations
  • But catches issues early (cheaper than debugging later)

Red Flags

  • Never:
  • Skip code review between tasks
  • Proceed with unfixed Critical issues
  • Dispatch multiple implementation subagents in parallel (conflicts)
  • Implement without reading plan task
  • If subagent fails task:
  • Dispatch fix subagent with specific instructions
  • Don't try to fix manually (context pollution)

Overview

Execute plan by dispatching fresh subagent per task, with code review after each. Core principle: Fresh subagent per task + review between tasks = high quality, fast iteration

Integration

  • Required workflow skills:
  • writing-plans - REQUIRED: Creates the plan that this skill executes
  • requesting-code-review - REQUIRED: Review after each task (see Step 3)
  • finishing-a-development-branch - REQUIRED: Complete development after all tasks (see Step 7)
  • Subagents must use:
  • test-driven-development - Subagents follow TDD for each task
  • Alternative workflow:
  • executing-plans - Use for parallel session instead of same-session execution

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

7-day trend score
0

Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/industrial/_project-template/skill-subagent-driven-development/badge)](https://verified-skill.com/skills/industrial/_project-template/skill-subagent-driven-development)

Something wrong with this skill or its page? Tell us.