subagent-driven-development

Automate subagent-driven development with fresh subagents per task and automated reviews.

205|26|Updated Oct 30, 2025
One-click install
npx skills add https://github.com/LerianStudio/ring --skill subagent-driven-development-lerianstudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/LerianStudio/ring/tree/main/default/skills/subagent-driven-development
Command: npx skills add https://github.com/LerianStudio/ring --skill subagent-driven-development-lerianstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autonomous plan execution using fresh subagents per task with automated reviews between tasks.

Core Features & Use Cases

  • Fresh subagent per task; automatic review gates
  • Parallel execution and fast iteration
  • Clear feedback loop and quality control

Quick Start

Launch a plan and let subagents execute tasks with automated reviews between steps.

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 execution with parallel reviews between steps?

Subagent-driven development automates task execution by deploying a fresh subagent per task, then runs parallel code, business logic, and security reviews between steps. This eliminates context pollution and accelerates high-quality execution across independent tasks within the same session.

Can I execute multiple tasks in parallel with automated quality gates?

Yes. The Skill dispatches a fresh subagent per task and aggregates review issues by severity, inserting TODO/FIXME notes and committing changes before advancing to the next task. Parallel execution and automated review gates ensure fast iteration with quality control.

What's the best way to structure plan execution with continuous between-task reviews?

Load your plan into TodoWrite, dispatch a Task tool per independent task with instructions, then trigger parallel reviews by code-reviewer, business-logic-reviewer, and security-reviewer. The Skill aggregates findings, inserts notes, commits, and advances automatically.

When should I use fresh subagents instead of a single context for all tasks?

Use fresh subagents per task when executing independent tasks requiring continuous progress and automated quality gates. This prevents context pollution, maintains focus, and enables true parallel execution—ideal for high-throughput development workflows.

Does this approach work for dependent tasks or only independent ones?

Subagent-driven development is optimized for independent tasks within the same session where each task can be isolated. Dependent tasks requiring sequential handoffs are not the primary use case; the Skill excels at parallel, quality-gated execution.