executing-plans

Execute phase-N task waves with dependency ordering and failure handling.

Updated Mar 17, 2026
One-click install
npx skills add https://github.com/steven-3/supermind --skill executing-plans-steven-3
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/steven-3/supermind/tree/main/skills/executing-plans
Command: npx skills add https://github.com/steven-3/supermind --skill executing-plans-steven-3

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the risk and confusion of running multi-step implementation plans by coordinating parallel task execution, recording progress, and handling failures deterministically.

Core Features & Use Cases

  • Wave-based parallel execution: Groups tasks into dependency-aware waves and dispatches executor subagents concurrently with a configurable maxParallel limit.
  • Progress tracking and verification: Updates phase progress tables in .planning/phases/phase-N/progress.md and performs post-wave conflict checks plus test/verification gates.
  • Failure handling with escalation paths: Debugger-based recovery for single-task failures, cascade skipping for dependency failures, and a hard stop for multiple failures in the same wave.

Quick Start

Use the orchestrator Execute phase to run .planning/phases/phase-N/ plans and tasks with executing-plans so each wave is executed in fresh-context subagents with progress captured in progress.md.

Frequently Asked Questions about executing-plans

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

FAQPage Schema
How do I execute parallel implementation tasks while respecting a dependency graph?

Wave-based plan execution coordinates parallel implementation tasks by topological sorting tasks into dependency-aware waves and dispatching them concurrently in fresh-context executor subagents with a configurable maxParallel limit.

How is task progress tracked during multi-phase plan execution?

Task progress is tracked by updating phase progress tables within the .planning/phases/phase-N/progress.md file using formatWaveProgress, recording completion status after each dispatched wave finishes.

What happens when a task fails during parallel wave execution?

Failure handling depends on scope: single-task failures trigger debugger-based recovery, dependency failures cause cascade skipping of downstream tasks, and multiple simultaneous failures in the same wave enforce a hard stop.

Do I need specific file structures for orchestrator execution phases?

Yes, orchestrator execution requires tasks to be defined as phase-N task specs located under the .planning/phases/phase-N/ directory so they can be dispatched atomically through executor.js in fresh-context subagents.

Can I run post-wave conflict checks and test verification gates automatically?

Yes, the execution process applies post-wave conflict checks and test verification gates after a wave completes, validating implementation correctness before proceeding to the next dependency wave.