gsd:execute-phase

Coordinate parallel phase task execution with checkpointing and atomic commits.

Updated Mar 15, 2026
One-click install
npx skills add https://github.com/cshyang/nochore --skill gsd-execute-phase-cshyang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd:execute-phase
Source: https://github.com/cshyang/nochore/tree/main/capabilities/incubator/skills/gsd/commands/execute-phase
Command: npx skills add https://github.com/cshyang/nochore --skill gsd-execute-phase-cshyang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end execution of phase tasks by coordinating waves of parallel work using the gsd-executor agent.

Core Features & Use Cases

  • Wave-based parallel execution: runs independent tasks in parallel while respecting dependencies.
  • Phase planning and checkpointing: loads phase-plan.md and validates progress between waves.
  • Atomic commits and deviation handling: ensures per-task commits and automatic handling of bugs, missing functionality, or blocking scenarios.

Quick Start

Load phase-plan.md and initiate wave-based execution with the gsd-executor agent.

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 independent phase tasks in parallel during development?

To execute independent phase tasks in parallel, orchestrate wave-based execution that coordinates parallel work while respecting task dependencies and validating progress between checkpoints.

What is wave-based execution for phase planning and task coordination?

Wave-based execution for task coordination is a method that runs independent tasks in parallel waves while respecting dependencies, ensuring atomic commits and handling deviations between waves.

How do I manage deviations and bugs during automated phase task execution?

Manage deviations during automated phase task execution by using an orchestration mechanism that automatically handles bugs, missing functionality, and blocking scenarios while creating atomic commits per task.

Do I need a phase-plan.md file to start wave-based parallel execution?

Yes, wave-based parallel execution requires loading a phase-plan.md file to identify independent tasks, coordinate execution waves, and verify progress checkpoints across development workflows.

What's the best way to handle checkpointing between parallel execution waves?

The best way to handle checkpointing between parallel execution waves is to validate progress after each wave completes, ensuring atomic commits are made per task before proceeding to dependent work.

When should I not use wave-based parallel execution for task coordination?

Wave-based parallel execution is not suitable when tasks lack independence or when phase-plan.md cannot be loaded, as the mechanism relies on identifying independent tasks and validating dependencies between waves.