aiox-wave-execute

Orchestrates parallel story execution waves using DAG planning and file-ownership batching.

3.1k|952|Updated Dec 9, 2025
One-click install
npx skills add https://github.com/SynkraAI/aios-core --skill aiox-wave-execute
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiox-wave-execute
Source: https://github.com/SynkraAI/aios-core/tree/main/.grok/skills/aiox-wave-execute
Command: npx skills add https://github.com/SynkraAI/aios-core --skill aiox-wave-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multiple development stories in parallel often leads to file conflicts, broken dependency order, and manual merge chaos. This Skill plans a wave of stories as a dependency DAG, partitions them into non-conflicting batches, and dispatches each story through the full-sdc development cycle with a controlled fan-in and merge handoff.

Core Features & Use Cases

  • Deterministic Wave Planning: Builds a story DAG via topological sort on depends_on and partitions batches by File List overlap using the aiox wave CLI.
  • Batch Dispatch with full-sdc: Runs each story through the full-sdc execute protocol, in parallel when multi-agent spawning is available or sequentially as a fallback.
  • Fan-in and Merge Handoff: Re-checks file conflicts across branches before merge and hands off PR/merge exclusively to the @devops agent.
  • Use Case: Given an epic with five stories, run aiox wave from-epic to generate a yolo-mode plan, dispatch ready stories in parallel batches, cascade-block dependents of failed stories, and produce a wave report for the devops merge step.

Quick Start

Ask the agent to execute wave WAVE-1 with your story files in yolo mode, for example: run wave-execute WAVE-1 with stories story-a.md and story-b.md in yolo mode with a dry run first.

Frequently Asked Questions about aiox-wave-execute

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

FAQPage Schema
How do I run multiple stories in parallel with aiox wave?

Use `aiox wave plan --stories a.md,b.md --wave-id WAVE-1 --mode yolo --save` to build the DAG and batches, then dispatch each story through the full-sdc skill. Stories with non-overlapping File Lists run in the same parallel batch.

How does wave-execute prevent file conflicts between parallel stories?

The planner partitions stories so that only non-overlapping File Lists run in the same batch; overlapping stories are deferred to later batches. A fan-in stage re-checks conflicts across branches before merge and surfaces them to a human and @devops.

What happens when a story fails during wave execution?

A failed story is marked via `aiox wave mark WAVE-1 {story-id} --status failed`, and any story that depends on it is marked blocked in the wave report rather than faked green. Independent later batches continue if their dependencies are satisfied.

Does wave-execute support a dry run before dispatching agents?

Yes, the `--dry-run` flag prints the computed plan and stops before any dispatch. Interactive mode also pauses for confirmation between batches, while yolo mode auto-confirms the plan.

What are the limitations of the wave-execute skill?

It does not include cockpit wave launch, conductor loops, or worktree registry features, and it depends on the full-sdc skill plus the aiox wave/sdc CLI. Yolo dispatch also requires a positive AIOX_MODEL_BUDGET_CEILING_USD value.