EXECUTE a lean wave — plan story DAG + file-ownership batches via CLI, dispatch full-sdc per story, fan-in check, hand off merge to @devops. Use when: wave-execute, run wave, epic wave, parallel stories SDC.
Run a wave of stories: deterministic plan (DAG + file partition) → dispatch
/full-sdc (or aiox sdc + skills) per story → fan-in → @devops merge-back.
Not in scope: cockpit wave launch, conductor loops, product worktree WL registry, companion spawn surface.
Depends on skill full-sdc and CLI aiox wave / aiox sdc.
/wave-execute {wave-id} --stories path1.md,path2.md [yolo|interactive] [--dry-run] [--no-confirm]
# pure CLI plan
aiox wave plan --stories path1.md,path2.md --wave-id {wave-id} --mode yolo --save
aiox wave next {wave-id}Yolo/parallel dispatch requires a positive explicit
AIOX_MODEL_BUDGET_CEILING_USD. Each child intent is scanned and bound to its
existing story before a model executor is invoked.
# From epic directory (C3) — preferred
aiox wave from-epic --epic-dir docs/framework/epics/core-super-update \
--filter 'CORE-SU.C' --wave-id CORE-SU-C --mode yolo
# Or explicit paths
aiox wave plan --stories a.md,b.md,c.md --wave-id WAVE-1 --mode yolo --save
# Advance / next batch (auto-completes stories already Done / sdc completed)
aiox wave advance WAVE-1
aiox wave next WAVE-1
# After a child full-sdc finishes or fails
aiox wave mark WAVE-1 {story-id} --status completed
aiox wave mark WAVE-1 {story-id} --status failed --notes "qg breaker"
# Report
aiox wave report WAVE-1
aiox wave status WAVE-1
# Per story (child full-sdc)
aiox sdc plan {story} --mode yolo
aiox sdc next {story}
# … run skill for phase …
aiox sdc verify {story} {phase} --markState: .aiox/waves/{wave-id}/state.json
Controller: wave-run.js + dispatch-adapter.js (C2) + epic-glue.js (C3)
aiox wave plan … --save — do not re-invent the DAG by grepping in prose.executor == quality_gate when those fields exist.--dry-run → print plan and stop.Show batches (parallel vs sequenced by file ownership). Get human OK unless --no-confirm or mode yolo.
For each batch in order:
runWaveBatch; its dispatch adapter must return governance evidence before the worker is invokedfull-sdc / /aiox-full-sdc)spawn_subagent with aiox-master (or dedicated coordinator) prompt:
Execute full-sdc on {story-path} mode={mode}. Use aiox sdc plan/next/verify. Do not git push.completed (or HALT).dependsOn A and A failed → mark B blocked in the wave report (do not fake green).Before merge:
@devops; never silent overwrite.Hand off to @devops only (push/PR/merge exclusive). Provide handoff:
handoff:
from: wave-execute
to: devops
wave_id: "{wave-id}"
stories: ["…"]
branches: ["feat/…"]
next_action: "create/merge PRs per repo policy"depends_on (deps outside the wave = already satisfied).| Mode | Behavior |
|---|---|
interactive | Confirm plan; pause between batches |
yolo | Auto-confirm plan; autonomous full-sdc children |
--dry-run | Plan only |
errors non-empty (cycle)0b32b68
Also appears in
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.