subagent-driven-development

Dispatch fresh subagents for independent tasks within the same session.

31|3|Updated Dec 12, 2025
One-click install
npx skills add https://github.com/JeremyDev87/codingbuddy --skill subagent-driven-development-jeremydev87
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/JeremyDev87/codingbuddy/tree/main/packages/rules/.ai-rules/skills/subagent-driven-development
Command: npx skills add https://github.com/JeremyDev87/codingbuddy --skill subagent-driven-development-jeremydev87

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executing complex implementation plans often requires handling many independent tasks without leaking context between them. This skill enables you to dispatch fresh subagents for each task within the same session, ensuring isolation, faster iteration, and robust review loops.

Core Features & Use Cases

  • Fresh subagent per task to avoid context pollution and maintain task-specific memory.
  • Two-stage reviews after each task: first check spec compliance, then verify code quality.
  • In-session orchestration for rapid feedback across multiple parallel or sequential tasks.
  • Suitable for plan-driven development, exploratory builds, and large feature implementations.

Quick Start

To start, initiate your plan-driven session and let the system dispatch subagents for each task.

Frequently Asked Questions about subagent-driven-development

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

FAQPage Schema
What is subagent-driven development for automating plan execution?

Subagent-driven development automates plan execution by dispatching fresh subagents to handle independent tasks within the same session, ensuring context isolation, faster iteration, and robust review loops.

How do I isolate context for independent tasks during in-session orchestration?

You isolate context by dispatching a fresh subagent for each independent task within the same session, preventing context pollution and maintaining task-specific memory during rapid iteration.

How does the two-stage code review process work for subagent tasks?

The two-stage review process first checks spec compliance for the completed task, then verifies code quality, supporting controlled escalation and re-review loops if standards are not met.

Can I use per-task specialist subagents for multidisciplinary planning scenarios?

Yes, you can dispatch per-task specialist subagents for multidisciplinary planning scenarios where tasks are largely independent and require rapid iteration, reviews, and context isolation.

When should I avoid using fresh subagents for plan-driven development?

You should avoid this approach if your implementation plan involves highly dependent tasks rather than largely independent ones, as the system relies on context isolation and in-session orchestration for rapid feedback.