wave

Orchestrate iterative wave-based task dispatch with code-dispatcher parallel execution.

7|1|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/makoMakoGo/code-dispatcher-toolkit --skill wave
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wave
Source: https://github.com/makoMakoGo/code-dispatcher-toolkit/tree/main/skills/wave
Command: npx skills add https://github.com/makoMakoGo/code-dispatcher-toolkit --skill wave

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured policy for orchestrating complex, multi-step tasks by breaking them down into iterative "waves" of parallelizable work, ensuring efficient execution and clear progress tracking.

Core Features & Use Cases

  • Iterative Dispatch: Manages tasks in successive rounds (waves), allowing for replanning based on previous wave's outcomes.
  • Parallel Execution: Leverages code-dispatcher --parallel to execute independent tasks within a wave concurrently.
  • Strict Scoping: Enforces mutually exclusive file scopes for tasks within the same wave to prevent conflicts.
  • Use Case: Refactoring a large codebase where changes in one module might affect others. You can dispatch initial refactoring tasks in wave 1, review the results, and then plan subsequent waves for dependent changes or bug fixes.

Quick Start

Use the wave skill to dispatch a set of independent tasks for wave 1, ensuring each task has a unique file scope.

Frequently Asked Questions about wave

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

FAQPage Schema
How do I orchestrate parallel task execution for large codebase refactoring?

Iterative wave-based dispatch manages complex multi-step tasks by breaking them down into successive rounds of parallelizable work. Each wave executes independent tasks concurrently, reviews the results, and then replans subsequent waves for dependent changes or bug fixes.

How do I prevent file conflicts during parallel code dispatch?

To start an iterative wave-based workflow, dispatch a set of independent tasks for wave 1 using code-dispatcher, ensuring each task has a unique file scope. Review the results after execution to plan and dispatch subsequent waves for dependent changes.

Does wave-based task management enforce hard rules on task prerequisites?

You should not use parallel task dispatch when your tasks lack mutually exclusive file scopes or have unresolved dependencies. The orchestration policy requires strict file scope mutual exclusion and clear task prerequisites to ensure deterministic workflow management.

What is the best way to manage iterative development workflows with dependent tasks?

Yes, you can replan dependent changes by reviewing previous wave outcomes. The iterative wave-based dispatch policy allows you to assess the results of a completed wave of parallel tasks before planning and executing subsequent waves for dependent modifications.