One-click install
npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-execute-phase-jedmamosto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-execute-phase
Source: https://github.com/jedmamosto/m-and-ms/tree/main/.agents/skills/gsd-execute-phase
Command: npx skills add https://github.com/jedmamosto/m-and-ms --skill gsd-execute-phase-jedmamosto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the coordination problem of executing many plans within a phase efficiently while respecting dependencies, pacing, and verification gates.

Core Features & Use Cases

  • Wave-based parallel execution: Groups plans into waves and runs them with subagents for controlled concurrency.
  • Optional wave filtering: Supports running only a specific wave (for staged rollout, quota management, or pacing) while still enforcing phase completion only when remaining plans are fully complete.
  • Gap-focused execution: Enables executing only gap-closure plans (plans marked with gap_closure: true) after prior verification creates fixes.
  • Interactive sequential mode: Supports an inline, checkpoint-driven execution path for small phases, bug fixes, or verification gaps.
  • Lean orchestrator, full context in subagents: Keeps the orchestrator within a ~15% context budget and gives each subagent a fresh 100% context to handle its assigned plan.

Quick Start

Run gsd-execute-phase for the target phase number and optionally restrict execution to a single wave to pace progress.

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 while respecting dependencies?

Wave-based parallel execution groups plans into dependency-respecting waves and runs them concurrently using subagents. This coordinates many plans efficiently while preserving workflow gates, pacing, and completion verification across the entire phase.

What is wave-based parallelization for phase execution?

Wave-based parallelization is an orchestration method that groups plans into sequential waves based on dependencies, running each wave's plans concurrently via subagents. It enforces workflow gates and checkpoints while maximizing throughput for multi-plan phases.

How do I run only a specific wave of plans to pace execution progress?

You can restrict execution to a single wave for staged rollout, quota management, or pacing. The orchestrator runs only that wave's plans while still enforcing phase completion only when all remaining plans across other waves are fully complete.

Can I execute only gap-closure plans after a verification failure?

Yes, gap-focused execution mode runs only plans marked with gap_closure: true. This targets specific fixes generated after prior verification failures, skipping already-satisfied plans to efficiently close workflow gaps.

How does the orchestrator manage context budget when handling multiple subagents?

The lean orchestrator stays within a roughly 15% context budget while spawning subagents. Each subagent receives a fresh 100% context window to handle its assigned plan using a full execute-plan context, preventing context overflow during parallel execution.

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

Interactive sequential mode suits small phases, bug fixes, or verification gaps requiring checkpoint-driven control. It provides an inline execution path as an alternative to parallel waves when you need tighter, step-by-step oversight of plan completion.