execute-set

Coordinate parallel wave execution with serialized Git commits and WAVE-COMPLETE.md re-entry detection.

4|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/pragnition/RAPID --skill execute-set
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: execute-set
Source: https://github.com/pragnition/RAPID/tree/main/skills/execute-set
Command: npx skills add https://github.com/pragnition/RAPID --skill execute-set

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating end-to-end execution of a wave set by parallelizing independent waves and serializing Git commits to prevent index corruption.

Core Features & Use Cases

  • Parallel wave execution: dispatch independent waves concurrently where possible.
  • Re-entry & verification: detect completed waves via WAVE-COMPLETE.md markers and validate commits to resume safely.
  • Plan-driven orchestration: drive execution using per-wave PLAN.md files with optional gap-closure and verification workflows.

Quick Start

Invoke /rapid:execute-set {SET_INDEX} to begin executing all waves in the specified set.

Frequently Asked Questions about execute-set

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

FAQPage Schema
How do I automate parallel execution of independent tasks without corrupting my Git index?▼

Automate parallel execution by dispatching independent waves concurrently while enforcing serialized Git commits. This prevents index corruption by ensuring only one wave writes to the repository at a time.

How do I resume an interrupted orchestration workflow from the last completed step?▼

Resume an interrupted orchestration workflow by detecting re-entry points using WAVE-COMPLETE.md markers and commit history. The system automatically identifies the correct wave to restart from safely.

How does DAG-based batching work for orchestrating concurrent waves?▼

DAG-based batching orchestrates concurrent waves by mapping dependencies into a directed acyclic graph. Independent waves are grouped and dispatched in parallel, while dependent waves wait for prerequisite completion.

How do I structure planning files to drive automated wave execution?▼

Structure planning files by creating per-wave PLAN.md documents that define execution steps. These plans drive the orchestration, managing state transitions and coordinating optional gap-closure and verification workflows.

Can I use this orchestration method for coordinating gap-closure and verification workflows?▼

Yes, you can use this orchestration method for gap-closure and verification workflows. It coordinates these processes as needed during end-to-end set execution, ensuring all waves meet verification criteria.

Why does parallel wave execution require serialized Git commits?▼

Parallel wave execution requires serialized Git commits to prevent index corruption. Concurrent writes to the same Git index would cause conflicts, so commits are strictly queued sequentially.