gsd-execute-phase

Coordinate wave-based parallel execution of dependent phase plans.

8|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-execute-phase-d0nmega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-execute-phase
Source: https://github.com/D0NMEGA/donnyclaude/tree/main/packages/skills/gsd-execute-phase
Command: npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-execute-phase-d0nmega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase execution can become a bottleneck when many plans with dependencies require careful sequencing. This skill orchestrates wave-based parallel execution to maximize throughput while preserving correctness.

Core Features & Use Cases

  • Discover and group plans into waves based on dependencies and readiness.
  • Spawn subagents to execute each wave, while the orchestrator coordinates results and verification.
  • Support optional flags such as --wave, --gaps-only, and --interactive for pacing, filtering, and debugging.
  • Use cases include large-phase automation, staged rollouts, and phased verification loops.

Quick Start

Provide the phase number and any flags to run the phase, and the skill will orchestrate wave-based parallel execution of all phase plans.

Frequently Asked Questions about gsd-execute-phase

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

FAQPage Schema
How do I execute phase plans with dependency-aware parallelism to reduce overall run time?

Execute phase plans with wave-based parallelism by grouping dependent tasks into sequential waves. The orchestrator spawns subagents for each wave, coordinating results and verification to maximize throughput while preserving governance gates and correctness.

What is wave-based parallel orchestration for staged plan execution?

Wave-based parallel orchestration is a technique that discovers and groups plans into execution waves based on dependencies and readiness. It enables selective wave execution, phase verification, and optional interactive or gaps-only modes to pace, filter, and debug staged rollouts.

Can I run a specific wave or only execute gaps in a phase plan?

Yes, you can target a specific wave or execute gaps only by passing the --wave and --gaps-only flags. These optional flags allow you to filter and debug specific stages of the phase execution without running the entire plan from scratch.

How do I debug phase execution bottlenecks in large automation workflows?

Debug phase execution bottlenecks by using the --interactive flag to pace the staged rollout. This pauses orchestration between waves, allowing you to inspect subagent results, verify state updates, and validate routing before proceeding to the next dependency stage.

Does phase orchestration preserve verification gates and state updates during parallel execution?

Yes, wave-based phase orchestration explicitly preserves governance gates such as verification, state updates, and routing. The orchestrator enforces explicit flag handling and reads per-wave data to ensure correctness is maintained across all parallel subagent executions.