Skip to content
Back to skills

Subagent Driven Development

ASecurity

Use when executing implementation plans with independent tasks in the current session

  • 47 stars
  • 0 votes
  • 0 copies
  • 6 views
  • Added September 12, 2026
code-quality

Security analysis

A100/100

Pro scans all 4 files and shows the line behind each finding

Scanned September 12, 2026

npx -y skills add skeletorflet/opencode-supreme-setup --skill subagent-driven-development --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Subagent Driven Development?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Subagent Driven Development
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/skeletorflet-subagent-driven-development/badge)](https://www.skillsdirectory.com/skills/skeletorflet-subagent-driven-development)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: subagent-driven-development
description: Use when executing implementation plans with independent tasks in the current session
---

# Subagent-Driven Development

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 + two-stage review (spec then quality) = high quality, fast iteration

**Continuous execution:** Do not pause to check in with your human partner between tasks. Execute all tasks without stopping.

## When to Use

Use when you have an implementation plan with mostly independent tasks in the same session.

vs. Executing Plans (parallel session): Same session, fresh subagent per task, two-stage review, faster iteration.

## The Process

For each task:
1. Dispatch implementer subagent with full task text and context
2. Implementer can ask questions before starting
3. Implementer implements, tests, commits, self-reviews
4. Dispatch spec compliance reviewer subagent
5. If spec issues found → implementer fixes → re-review
6. Dispatch code quality reviewer subagent
7. If quality issues found → implementer fixes → re-review
8. Mark task complete

After all tasks: Dispatch final code reviewer, then use finishing-a-development-branch.

## Handling Implementer Status
- DONE: Proceed to spec compliance review
- DONE_WITH_CONCERNS: Read concerns, address before review
- NEEDS_CONTEXT: Provide missing context, re-dispatch
- BLOCKED: Assess blocker, re-dispatch with better model or break task

## Red Flags
Never: Skip reviews, proceed with unfixed issues, dispatch multiple implementers in parallel, start code quality before spec compliance is done.

Files in this skill

  • SKILL.md1.7 KB
  • code-quality-reviewer-prompt.md513 B
  • implementer-prompt.md1.1 KB
  • spec-reviewer-prompt.md634 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.