subagent-driven-development

Dispatch fresh subagents per task with two-stage spec and code reviews.

Updated Apr 16, 2026

Search Tags:#workflow #planning #tdd #delegation #review #code-quality #subagent

Ready to run

npx skills add https://github.com/jacardl/New-Radar --skill subagent-driven-development-jacardl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/jacardl/New-Radar/tree/main/backend/frameworks/hermes-agent/skills/software-development/subagent-driven-development
Command: npx skills add https://github.com/jacardl/New-Radar --skill subagent-driven-development-jacardl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executes implementation plans by dispatching fresh subagents per task and enforcing a two-stage review process to ensure spec compliance and code quality.

Core Features & Use Cases

Fresh subagent per task to prevent context bleed and ensure task isolation.
Two-stage review: first check spec compliance, then assess code quality.
End-to-end task orchestration from plan interpretation to completed tasks and final integration checks.
Works with writing-plans and test-driven development workflows to align planning and execution.

Quick Start

Read your implementation plan and dispatch the first task to a fresh subagent to begin the two-stage review cycle.

Frequently Asked Questions about subagent-driven-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I execute implementation plans with isolated subagents to prevent context bleed?▼

Executing implementation plans with isolated subagents requires dispatching a fresh subagent per task with complete context. This approach prevents context bleed across independent tasks, ensuring clean task isolation and reducing cross-task contamination during code execution.

What is a two-stage review process for code quality and spec compliance?▼

A two-stage review process first checks spec compliance to verify the implementation meets requirements, then assesses code quality. This ensures subagent-driven development produces functional code that adheres to both the original plan and quality standards.

How do I delegate independent tasks to subagents while maintaining code quality?▼

To delegate independent tasks, use delegate_task to dispatch each task with complete context to a fresh subagent. Follow this with spec-compliance and code-quality reviews, plus final integration checks to ensure the overall implementation maintains high standards.

Does subagent-driven development work with test-driven development workflows?▼

Subagent-driven development works with test-driven development and writing-plans workflows to align planning and execution. It orchestrates subagents to execute the plan while applying two-stage reviews, ensuring TDD specs are met and code quality is maintained.

When should I use fresh subagents for task delegation in software engineering?▼

Use fresh subagents for task delegation when working with implementation plans that have multiple independent tasks. This approach is ideal when two-stage reviews are desired and when fresh context per task is needed to reduce cross-task contamination.

What are the limitations of dispatching fresh subagents per task?▼

Dispatching fresh subagents per task is limited to plans with multiple independent tasks. It is not suitable for highly interdependent tasks where context sharing is required, as the isolation mechanism prevents cross-task contamination but also restricts shared context.