gsd-execute-phase

Orchestrate phase-level plan execution with wave-based parallelism and subagents.

1|Updated Aug 17, 2025
One-click install
npx skills add https://github.com/DuySeu/StockMind --skill gsd-execute-phase-duyseu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-execute-phase
Source: https://github.com/DuySeu/StockMind/tree/main/.agent/skills/gsd-execute-phase
Command: npx skills add https://github.com/DuySeu/StockMind --skill gsd-execute-phase-duyseu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates the execution of multiple plans within a phase using wave-based parallelism to reduce orchestration overhead and speed up delivery.

Core Features & Use Cases

  • Wave-based plan discovery and dependency analysis to group tasks into executable waves.
  • Subagent orchestration: spawn isolated workers that load full phase context and return results.
  • Phase filtering with optional flags like --wave to pace rollout and meet quota constraints.
  • Checkpointing and state consistency across waves to preserve progress and recover from failures.

Quick Start

Execute all plans in the current phase using wave-based parallel 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 interdependent plans in parallel to speed up workflow delivery?

Wave-based parallel execution groups interdependent plans into executable waves, spawning isolated subagents to process tasks concurrently within each wave to accelerate workflow delivery.

What is wave-based plan execution and how does it reduce orchestration overhead?

Wave-based plan execution analyzes task dependencies to group plans into executable waves, allowing parallel subagent processing and minimal orchestration overhead while preserving state consistency across waves.

How do I pace plan rollout to meet quota constraints during phase execution?

Apply optional phase filtering flags like --wave during execution to limit the scope of spawned subagents, pacing plan rollout to meet specific quota constraints.

Does this orchestration approach preserve progress and recover from subagent failures?

The orchestration mechanism preserves progress and recovers from failures by maintaining state consistency and utilizing checkpoints across each executed wave of plans.

Can I use subagent orchestration for complex workflows with many interdependent tasks?

Subagent orchestration is designed for complex workflows, spawning isolated workers that load full phase context, evaluate interdependent tasks, and return collected results efficiently.