subagent-driven-development

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

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/afel6/scal-ai-pipeline --skill subagent-driven-development-afel6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/afel6/scal-ai-pipeline/tree/main/hermes_skills_library/software-development/subagent-driven-development
Command: npx skills add https://github.com/afel6/scal-ai-pipeline --skill subagent-driven-development-afel6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables teams to execute implementation plans by delegating independent tasks to fresh subagents, ensuring rigorous two-stage reviews for specification and quality.

Core Features & Use Cases

  • Fresh subagent per task to keep context clean and prevent state leakage.
  • Two-stage reviews: first spec compliance, then code quality, catching issues early.
  • Scalable automation for planning-driven workflows with parallel task execution when tasks are independent.

Quick Start

Dispatch a fresh subagent for each task, then route results to a spec compliance reviewer and a code-quality reviewer before marking tasks complete.

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema
How do I automate task delegation to subagents for implementation plans?

You can automate task delegation by dispatching a fresh subagent for each independent task to execute implementation plans, preventing state leakage and ensuring clean context for strict spec compliance.

What is the best way to run automated code reviews on delegated tasks?

The best way to run automated code reviews on delegated tasks is using a two-stage process: first checking spec compliance, then evaluating code quality to catch issues early before marking tasks complete.

How does using a fresh subagent per task prevent context state leakage?

Using a fresh subagent per task prevents context state leakage by keeping the working context clean for each independent implementation, avoiding residual data from previous tasks affecting current execution.

When do I need a two-stage review workflow for subagent task execution?

You need a two-stage review workflow for subagent task execution when your plan-driven development requires strict specification compliance and quality checks before outputs are marked as integration-ready.

Can I execute independent implementation tasks in parallel using subagents?

Yes, you can execute independent implementation tasks in parallel using subagents, as the workflow scales automation for planning-driven development where tasks are largely independent and require fresh context.

What are the limitations of plan-driven workflows with subagent delegation?

Plan-driven workflows with subagent delegation are limited to tasks that are largely independent and require strict spec compliance; highly interdependent tasks may not suit the fresh subagent per task model.