subagent-driven-development

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

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/brainworkup/skills --skill subagent-driven-development-brainworkup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/brainworkup/skills/tree/main/neuropsych-reports/references/luria-related-complement-skills/subagent-driven-development
Command: npx skills add https://github.com/brainworkup/skills --skill subagent-driven-development-brainworkup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Subagent-driven development enables executing plans by delegating tasks to isolated, specialized agents, reducing context leakage and accelerating iterations.

Core Features & Use Cases

  • Fresh subagent per task to avoid context pollution
  • Two-stage review: spec compliance then code quality
  • Flexible workflow with implementer, spec reviewer, and code quality reviewer roles

Quick Start

Dispatch a fresh subagent per task and run two-stage reviews to ensure spec compliance and code quality.

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema
How do I delegate tasks to subagents without context pollution?

Subagent-driven development prevents context pollution by dispatching a fresh, isolated subagent for each task. This orchestration approach executes complex plans with parallel or staged work while maintaining strict separation between tasks.

What is a two-stage review process for plan execution?

A two-stage review process enforces spec compliance first, then evaluates code quality. This workflow uses modular roles including implementer, spec reviewer, and code-quality reviewer to ensure tasks meet requirements before passing quality checks.

How do I orchestrate parallel tasks with independent subagents?

Orchestrate parallel tasks by dispatching independent subagents per task within a controlled workflow. This subagent-driven approach accelerates iterations by delegating specialized modular roles to handle complex, staged plan execution.

When should I use subagent-driven development for workflow automation?

Use subagent-driven development for complex plans requiring parallel or staged work with strict reviews across tasks. It reduces context leakage and accelerates iterations by isolating specialized agents for each delegated task.

Does subagent-driven development require dependencies or components?

Subagent-driven development requires no external dependencies or components. It applies to complex plans using a controlled workflow with modular roles like implementer, spec reviewer, and code-quality reviewer.

What are the limitations of using subagents for task delegation?

Subagent-driven task delegation is limited to complex plans requiring parallel or staged work with strict reviews. It enforces a controlled workflow with modular roles, which may not suit simple, single-step tasks without review needs.