subagent-driven-development

Dispatch fresh subagents for independent implementation tasks with two-stage reviews.

Updated May 6, 2026
One-click install
npx skills add https://github.com/Takfes/indie-scaffolder --skill subagent-driven-development-takfes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/Takfes/indie-scaffolder/tree/main/components/agent-skills-commands/.agents/skills/subagent-driven-development
Command: npx skills add https://github.com/Takfes/indie-scaffolder --skill subagent-driven-development-takfes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you execute implementation plans without losing focus by isolating each task in a fresh subagent, so complex work stays organized and reviewable in the same session.

Core Features & Use Cases

  • Fresh subagent per task: Assign each independent implementation task to a dedicated subagent with only the context it needs.
  • Two-stage review: Verify every task first for spec compliance, then for code quality before moving on.
  • Same-session coordination: Keep momentum while avoiding context pollution, making it well suited for multi-step feature work, refactors, and plan execution.

Quick Start

Use the subagent-driven-development skill to carry out your implementation plan by delegating each independent task to a fresh subagent and reviewing it in two stages before marking it 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 execute complex implementation plans without losing context in a single session?

You can execute implementation plans by dispatching a fresh subagent for each independent task, isolating context to keep complex work organized. This approach maintains momentum while preventing context pollution during multi-step feature work and refactors.

How does subagent-driven task execution handle code review?

Subagent-driven task execution applies a two-stage review process for every task, first verifying spec compliance and then checking code quality. This ensures each work item is reviewed and validated before moving on to the next task.

What is the best way to isolate independent code changes for iterative progress?

The best way to isolate independent code changes is assigning each work item to a dedicated subagent with only the context it needs. This allows task-by-task validation and self-review with issue fixes before final completion checks.

Do I need a specific framework to coordinate subagents for software engineering tasks?

No specific framework is required, as the skill operates with no dependencies. It coordinates implementation tasks by managing fresh subagents, spec-compliance reviews, and code-quality reviews within your same-session execution plans.

When should I use fresh subagents for implementation instead of a single continuous session?

You should use fresh subagents when you need isolated context for each independent work item to avoid context pollution. It is well suited for multi-step feature work, refactors, and execution plans requiring task-by-task validation.