subagent-driven-development

Executes implementation plans by dispatching fresh subagents per task with two-stage review.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/gyc-12/Archipelago --skill subagent-driven-development-gyc-12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-driven-development
Source: https://github.com/gyc-12/Archipelago/tree/main/modules/collaboration-runtime/src-tauri/experts/skills/subagent-driven-development
Command: npx skills add https://github.com/gyc-12/Archipelago --skill subagent-driven-development-gyc-12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Executing a multi-task implementation plan in one session often pollutes context, skips reviews, and stalls between tasks. This Skill orchestrates plan execution by dispatching a fresh subagent per task and enforcing spec compliance and code quality reviews after each task. ## Core Features & Use Cases - Fresh subagent per task: Each task runs in an isolated context with curated instructions, preventing context pollution and keeping the controller focused on coordination. - Two-stage review gates: A spec compliance reviewer verifies the code matches requirements before a code quality reviewer assesses maintainability, with fix-and-re-review loops until approval. - Status-based escalation handling: Implementer subagents report DONE, DONE_WITH_CONCERNS, NEEDS_CONTEXT, or BLOCKED, and the controller responds with more context, a more capable model, or task decomposition. - Use Case: Given a written plan with five independent tasks, execute all of them continuously in the current session, with each task implemented, tested, committed, and reviewed before moving on. ## Quick Start Use subagent-driven development to execute the implementation plan in docs/plans/feature-plan.md task by task with reviews after each task.

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 an implementation plan with subagents?

Read the plan once, extract all tasks with full text into a todo list, then dispatch an implementer subagent per task with the complete task text and context. After each task, run a spec compliance review followed by a code quality review before marking it complete.

What is the difference between subagent-driven development and executing plans in a parallel session?

Subagent-driven development stays in the same session with no context switch, uses a fresh subagent per task, and iterates faster without human-in-the-loop between tasks. Executing plans in a parallel session involves a handoff to a separate session.

When should I not use subagent-driven development?

Avoid it when there is no implementation plan yet, when tasks are tightly coupled and cannot run independently, or when you want execution in a separate parallel session. Brainstorm or write the plan first in those cases.

What happens when an implementer subagent reports BLOCKED?

The controller assesses the blocker: provide more context and re-dispatch for context problems, use a more capable model for reasoning-heavy tasks, break oversized tasks into smaller pieces, or escalate to the human if the plan itself is wrong.

Why must spec compliance review come before code quality review?

Spec compliance confirms the implementation matches requirements with nothing missing or extra, which must hold before judging code quality. Reviewing quality first wastes effort on code that may need rework to meet the spec.