Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/wave-executor
Use this skill when executing the agreed session plan in waves with role-based execution and parallel subagents. Handles inter-wave quality checks, plan adaptation, and progress tracking. Core orchestration engine for feature and deep sessions. Triggered by /go command.
Passed 15 of 19 test cases with the skill, and 4 of 19 without it.
and 15 more in the full report
13 fixed4 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
When the user approves a wave plan by executing `/go`, what transition status should be recorded in STATE.md for tasks previously listed as `brainstormed`?
| Checked | Without skill | With skill |
|---|---|---|
| Transitions mission status from brainstormed to validated upon /go approval. | Missed | Passed |
The instructions your model reads when the skill loads.
You are the coordinator. You do NOT implement — you orchestrate. Your job:
This harness exists to enable multi-agent coordination at scale — not by removing friction, but by making it visible, classifiable, and recoverable.
The wave-executor is process scaffolding around LLM agents. It handles task breakdown, scope enforcement, circuit breaker guards, and recovery patterns. Unlike direct chat with an agent, it trades flexibility for safety and repeatability across a bounded execution envelope.
Every harness creates friction. The goal is not minimum friction — it is useful friction that prevents higher-cost problems downstream.
Friction we accept:
wave-scope.json pre-dispatch setupFriction we prevent:
The harness does not hope agents self-correct. It detects stagnation patterns — pagination-spiral, turn-key-repetition, error-echo — classifies them into the Error-Class Taxonomy defined in circuit-breaker.md, and re-scopes mechanically. Review logic lives in wave-loop.md § "Review Agent Outputs".
State files live in the platform's native directory:
.claude/for Claude Code,.codex/for Codex CLI,.cursor/for Cursor IDE. All references to.claude/below should use the platform's state directory. Shared metrics (sessions.jsonl, learnings.jsonl) live in.orchestrator/metrics/— both platforms read and write there. Seeskills/_shared/platform-tools.mdfor tool mappings.
test cases passed, vs 4 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.