gsd-execute-phase

Execute phased plans via dependency-aware parallel wave orchestration.

1|Updated Sep 6, 2015
One-click install
npx skills add https://github.com/deerawan/dotfiles --skill gsd-execute-phase-deerawan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-execute-phase
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-execute-phase
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-execute-phase-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the friction of executing a multi-plan phase by orchestrating dependency-aware work in parallel waves, while preserving verification and workflow gates.

Core Features & Use Cases

  • Wave-based phase execution: Groups plans into execution waves to run in parallel without losing correctness.
  • Dependency-aware orchestration: Discovers plans, analyzes dependencies, and routes subagents so each handles its own plan with full execute context.
  • Optional execution modes: Supports wave filtering, gap-only execution, or an interactive sequential mode for small phases and verification gaps.

Quick Start

Run the phase executor for your target phase number and optionally restrict it to a specific wave for staged rollout.

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 multi-plan phases in parallel without breaking workflow gating?▼

Wave-based parallel orchestration groups dependency-safe plans into execution waves, running subagents concurrently to reduce wall-clock time while preserving verification gates.

What is dependency-aware phase execution and how does it group tasks?▼

Dependency-aware phase execution discovers plans, analyzes their dependencies, and routes them into safe parallel waves so independent tasks run concurrently without correctness loss.

Can I filter phase execution to run a specific wave or only fill verification gaps?▼

Yes, optional runtime flags support wave filtering for staged rollouts, gap-only execution to fill verification gaps, or interactive sequential mode for small phases.

Does subagent orchestration work with standard and filtered execution modes?▼

Subagent orchestration routes each plan to its own subagent with full execute context, handling both standard execution and filtered modes like wave-specific or gap-only runs.

When should I use interactive sequential mode instead of parallel wave execution?▼

Interactive sequential mode suits small phases or verification gap filling where dependency routing overhead outweighs wall-clock savings from parallel wave orchestration.

Why do I need runtime flag activation for phase execution workflows?▼

Runtime flag activation is strictly derived from arguments to ensure safe execution mode selection, preventing accidental parallel waves or filtered runs without explicit intent.