add-subagent-driven-development

Dispatch independent subagents for iterative development tasks with enforced code reviews.

8|2|Updated Mar 2, 2026

Search Tags:#automation #workflow #development #code review #task management #agent

Ready to run

npx skills add https://github.com/brabos-ai/code-addiction --skill add-subagent-driven-development

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-subagent-driven-development
Source: https://github.com/brabos-ai/code-addiction/tree/main/framwork/.codeadd/skills/add-subagent-driven-development
Command: npx skills add https://github.com/brabos-ai/code-addiction --skill add-subagent-driven-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the implementation of complex features by breaking them down into manageable tasks, executing each task with a fresh subagent, and enforcing code reviews between tasks to ensure high quality and rapid iteration.

Core Features & Use Cases

Task Decomposition: Breaks down a plan into atomic, executable tasks.
Subagent Orchestration: Dispatches independent subagents for each task, preventing context pollution.
Automated Code Review: Integrates code review after each task to catch issues early.
Use Case: Implementing a new user authentication flow involves creating database migrations, backend API endpoints, and frontend components. This Skill manages the execution of each part, ensuring code quality at every step.

Quick Start

Use the add-subagent-driven-development skill to implement the next task in the current plan.

Frequently Asked Questions about add-subagent-driven-development

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

FAQPage Schema

How do I automate code reviews between development tasks?▼

Automated code reviews between tasks are enforced by dispatching independent subagents for each discrete task, catching issues early before the next iteration begins. This prevents context pollution and maintains quality across complex feature implementations.

What is subagent-driven development for iterative workflows?▼

Subagent-driven development orchestrates iterative software execution by breaking down plans into atomic tasks and dispatching fresh subagents for each one. It requires a robust dispatch mechanism and structured decision logging to maintain context and track progress across tasks.

How do I decompose a complex feature into manageable development tasks?▼

Task decomposition breaks down a complex implementation plan into atomic, executable tasks suited for independent subagent execution. Each task is then orchestrated sequentially with integrated quality gates to ensure rapid iteration and high code quality.

Can I use subagent orchestration for multi-step feature implementation?▼

Subagent orchestration applies to feature implementation workflows requiring coordinated multi-agent execution, such as creating database migrations, backend API endpoints, and frontend components. It manages execution of each part while enforcing code reviews at every step.

Do I need a structured decision logging system for multi-agent task management?▼

A structured decision logging system is required to maintain context and track progress across tasks during subagent-driven development. It ensures that independent subagents remain coordinated throughout the iterative execution and quality gate cycles.

When should I avoid using subagents for iterative development?▼

Subagent-driven development should be avoided when a feature cannot be decomposed into discrete tasks or when a robust subagent dispatch mechanism is unavailable. It is designed for complex, multi-step implementations rather than simple, single-action code changes.