gsd-execute-phase

Coordinate multi-plan phase execution via wave-based parallel batches.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate end-to-end execution of multi-plan phases by discovering plans, analyzing dependencies, and running them in wave-based parallel batches.

Core Features & Use Cases

  • Wave-based parallel execution of plans within a phase
  • Subagent orchestration with deterministic task spawning and result collection
  • Flexible flags (--wave, --gaps-only, --interactive) to control flow and pacing
  • Context budgeting, routing, and checkpoint handling for robust workflows

Quick Start

Invoke the skill by mentioning $gsd-execute-phase followed by your phase arguments to start a wave-based execution

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 multiple workflow plans in parallel batches?

Wave-based phase execution coordinates multi-plan phases by analyzing dependencies and running them in wave-based parallel batches. It applies to complex phases with many plans and gates, spawning subagents to execute tasks and aggregate results.

Can I control the pacing of parallel workflow execution?

Yes, you can control pacing by passing flags like --interactive, --wave, or --gaps-only. These flags allow selective wave execution, gap closures, or sequential interactive runs across your workflows.

How does subagent orchestration handle context limits during phase execution?

Subagent orchestration enforces context budgets and routing rules during phase execution to manage limits. It deterministically spawns subagents for plan execution, aggregates results, and handles checkpoints to ensure reliable progress.

What is the best way to run only the missing parts of a multi-plan workflow?

The best way to run missing parts is using the --gaps-only flag for wave-based phase execution. It analyzes dependencies to identify and close gaps selectively within your workflow without re-running completed plans.

Does wave-based phase execution work for complex workflows with many gates?

Yes, wave-based phase execution is designed specifically for complex phases with many plans and gates. It orchestrates subagents, handles checkpoints, and applies context budgeting to ensure reliable progress at scale.