subagent-driven-development

Execute independent development tasks with isolated subagents and two-stage reviews.

54|7|Updated May 29, 2026
One-click install
npx skills add https://github.com/wibus-wee/cradle-app --skill subagent-driven-development-wibus-wee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/wibus-wee/cradle-app/tree/main/.agents/skills/subagent-driven-development
Command: npx skills add https://github.com/wibus-wee/cradle-app --skill subagent-driven-development-wibus-wee

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenges of executing complex implementation plans with independent tasks, ensuring high-quality, fast iteration without context pollution.

Core Features & Use Cases

  • Subagent-Based Execution: Dispatch fresh subagents per task, maintaining isolated contexts for focused work.
  • Two-Stage Review: Ensures spec compliance and code quality through separate reviews.
  • Continuous Execution: Execute all tasks without pauses, except for blocking issues or task completion.
  • Use Case: Ideal for software development workflows where tasks are modular and can be executed independently.

Quick Start

Use the subagent-driven-development skill to execute the 'feature-plan.md' plan with subagent-driven development.

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 independent tasks in parallel without context pollution?

To execute independent tasks without context pollution, dispatch fresh subagents per task to maintain isolated contexts. This approach ensures focused work and high-quality iteration during complex implementation plans.

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

A two-stage review process evaluates spec compliance and code quality through separate reviews. This mechanism ensures that subagent-driven task execution meets functional requirements while maintaining high coding standards.

How do I automate continuous execution of a modular software development plan?

Automate continuous execution by dispatching specialized subagents to execute all tasks without pauses. The system manages continuous execution automatically, only pausing when encountering blocking issues or completing tasks.

Can I use subagent-based execution for complex implementation plans with task decomposition?

Yes, you can use subagent-based execution for complex implementation plans. It supports task decomposition and utilizes review loops for error handling, ensuring high-quality iteration across modular and independent tasks.

Why does my AI coding session lose context when running multiple sequential tasks?

AI coding sessions lose context when running sequential tasks due to context pollution. Dispatching fresh subagents per task maintains isolated contexts, preventing previous task data from degrading execution quality.

When should I not use subagent-driven development for task execution?

You should avoid subagent-driven development when tasks are not modular or cannot be executed independently. The approach relies on task decomposition and isolated contexts, making it unsuitable for tightly coupled execution workflows.