subagent-execution

Orchestrate autonomous subagents to execute implementation plans with per-task isolation and two-stage review.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/heymishy/2x2-v3-28-03-20216 --skill subagent-execution-heymishy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: subagent-execution
Source: https://github.com/heymishy/2x2-v3-28-03-20216/tree/main/.github/skills/subagent-execution
Command: npx skills add https://github.com/heymishy/2x2-v3-28-03-20216 --skill subagent-execution-heymishy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrate autonomous subagents to execute an implementation plan with per-task isolation and two-stage review to maintain focus and quality.

Core Features & Use Cases

  • Fresh subagents per task with two-stage review (spec compliance followed by code quality) to accelerate delivery while ensuring accuracy.
  • Deterministic task isolation and context control, reducing cross-task leakage and confusion.
  • Use case: when an implementation plan exists and subagents are available to execute tasks in sequence.

Quick Start

Dispatch a fresh subagent for each task in the plan and perform two-stage reviews after every task.

Frequently Asked Questions about subagent-execution

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

FAQPage Schema
How do I automate execution of an implementation plan with subagents?

You can automate execution by dispatching a fresh, isolated subagent for each task in your implementation plan, followed by a two-stage review to ensure quality and traceability.

What is two-stage code review in autonomous subagent orchestration?

Two-stage review in subagent orchestration checks spec compliance first, then evaluates code quality, ensuring autonomous task execution maintains focus, accuracy, and adherence to the plan.

How do I isolate context between tasks during automated plan dispatch?

You isolate context by dispatching a fresh subagent for each task, preventing cross-task leakage and confusion while tracking workflow state to maintain deterministic execution.

When should I use subagent execution instead of a task-by-task flow?

Use subagent execution when a written implementation plan exists and subagents are available; if no subagents are available, use the task-by-task flow instead.

Does subagent execution work without a written implementation plan?

No, subagent execution applies when a written implementation plan already exists, serving as the required input to dispatch isolated subagents and perform sequential two-stage reviews.

Why does cross-task context leakage happen during automated code generation?

Cross-task leakage happens when context bleeds between tasks; using fresh subagents per task with deterministic isolation reduces confusion and maintains focus throughout the workflow.