gsd-execute-phase

Execute phase plans with wave-based parallelization and checkpoint handling.

Updated May 22, 2026
One-click install
npx skills add https://github.com/yusaduymaz/loexai --skill gsd-execute-phase-yusaduymaz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-execute-phase
Source: https://github.com/yusaduymaz/loexai/tree/main/.codex/skills/gsd-execute-phase
Command: npx skills add https://github.com/yusaduymaz/loexai --skill gsd-execute-phase-yusaduymaz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the coordination burden of running a phase made of many plans by organizing work, preserving execution order, and preventing skipped verification or state updates.

Core Features & Use Cases

  • Wave-based execution across multiple plans and subagents.
  • Optional selective modes for a single wave, gap-closing plans, or interactive sequential execution.
  • Use cases include releasing a phase incrementally, closing verification gaps, or executing a large batch of plans while preserving checkpoints and routing.

Quick Start

Use the gsd-execute-phase skill to run the current phase end to end with the appropriate wave or interactive flag.

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 parallel subagents without skipping verification?

Run orchestrated phase plans using wave-based parallelization across subagents. This workflow handles dependency analysis, checkpoint handling, result collection, and verification to coordinate execution without manual intervention.

What is wave-based parallel execution for phased delivery workflows?

Wave-based execution organizes a phase of multiple plans into coordinated batches run by subagents. It analyzes dependencies and enforces strict workflow gates, checkpoint handling, and state updates to preserve execution order.

Can I run a single wave or close verification gaps instead of executing the entire phase?

Selective modes allow executing a single wave, closing verification gaps, or running interactive sequential executions. These options support incremental phase releases without processing the entire batch of plans simultaneously.

How does checkpoint handling work during parallel subagent execution?

Checkpoint handling preserves execution state across subagents during wave-based parallelization. The workflow enforces strict gates, collects results, verifies outputs, and updates state before proceeding to subsequent waves.

When should I use interactive sequential execution instead of parallel waves?

Interactive sequential execution suits closing verification gaps or releasing phases incrementally. Use it when strict workflow gates require manual validation between steps, unlike parallel waves designed for large batch plan execution.