gpd-execute-phase

Executes all plans in a research phase using wave-based parallel subagent orchestration.

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-execute-phase-michaelsengineering
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gpd-execute-phase
Source: https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics/tree/main/.agents/skills/gpd-execute-phase
Command: npx skills add https://github.com/MichaelsEngineering/sentinel-multiscale-field-dynamics --skill gpd-execute-phase-michaelsengineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating the execution of many interdependent research plans within a phase is error-prone when done manually, especially when plans involve derivations, numerical simulations, data analysis, and LaTeX writing that must respect dependencies, conventions, and verification gates. ## Core Features & Use Cases - Wave-Based Parallel Execution: Discovers plans, analyzes dependencies, groups them into waves, and spawns executor subagents in parallel while detecting intra-wave dependency cycles and file-modification conflicts. - Phase Classification & Adaptation: Classifies phases as derivation, numerical, literature, paper-writing, formalism, analysis, or validation, then adapts context budgets, inter-wave checks, timeouts, and pre-execution agents accordingly. - Safety Gates & Checkpointing: Enforces convention locks, first-result gates, pre-fanout reviews, bounded execution segments, and git-tag wave checkpoints regardless of autonomy mode. - Use Case: A physics researcher with a planned phase containing five PLAN.md files runs the skill to execute them across two waves, with automatic verification, convention enforcement, and SUMMARY.md generation per plan. ## Quick Start Ask the AI to execute phase 1 with the gpd-execute-phase skill, optionally passing --gaps-only to run only gap-closure plans.

Frequently Asked Questions about gpd-execute-phase

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I execute all plans in a research phase in parallel?▼

Run the skill with a phase number, and it discovers plans, groups them into dependency-respecting waves, and spawns executor subagents in parallel. Use the --gaps-only flag to restrict execution to gap-closure plans only.

How does wave-based parallelization avoid dependency conflicts?▼

The skill validates that no plan depends on another plan in the same wave and checks files_modified frontmatter for overlaps between parallel plans. Intra-wave dependency conflicts halt execution, while file conflicts trigger a warning with an option to serialize.

Can I run phase execution without user confirmation prompts?▼

Yes, setting autonomy to yolo executes waves without prompts on clean passes, but required correctness gates, first-result sanity checks, and pre-fanout reviews still run. Derivation and validation phases additionally restrict yolo from skipping verification.

What happens if conventions are not locked before a derivation phase?▼

Execution halts with a hard gate error. Derivation and formalism phases require locked conventions because sign or convention errors compound irreversibly across every downstream step, and this gate applies in all autonomy modes.

Why does literature phase execution run sequentially instead of parallel?▼

Literature plans build on each other's findings, so parallel execution risks redundant searches and duplicated work. The phase classifier forces sequential execution within waves for literature-classified phases regardless of the parallelization config.