Menu
Wave task runner. Reads a wave.md file and runs each pipeline sequentially. Invoked as `$wave <path/to/wave.md>`. Argument is the path to the wave manifest file.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Cross-project build pipeline. Invoked as $wave-build <feature> or $wave-build with Pipeline/Task manifest/Wave args. Runs the full pipeline end to end including all git work.
Attributes Claude Code runtime token spend per sub-agent and per workflow run, parsed from local JSONL transcripts, and ranks the heaviest burners with estimated USD cost. Answers 'which agent burned the most tokens', 'what did this workflow/wave/pipeline cost', 'token breakdown', 'per-operation tokens', and any retrospective spend analysis. Triggered by 'token ledger', 'token attribution', 'heaviest token burner', 'which agent burned the most tokens', 'what did the run/workflow/wave cost', 'token breakdown', 'per-agent tokens', 'per-operation tokens'. Complements /pcm:context-meter: that audits STATIC context size, this covers RUNTIME spend attribution — route static-budget questions to context-meter, after-the-fact spend questions here.
Code hygiene audit — ghost fields, dead code, deps, arch, types, naming, quality. Domain-hydrated at install time.
Security deep scan — injection, auth, API, LLM/prompt, sensitive data, crypto, transport, supply-chain. Domain-hydrated at install time.
Exhaustive multi-angle analysis. Invoked by `360`, `three-sixty`, `do a 360`, "what could go wrong", or explicit blind-spot sweep requests.
RND goal-driven iteration. Invoked by `RND`, `research and develop`, `iterate until`, or "find the best approach for" a testable outcome.
| name | wave |
| description | Wave task runner. Reads a wave.md file and runs each pipeline sequentially. Invoked as `$wave <path/to/wave.md>`. Argument is the path to the wave manifest file. |
Read .claude/commands/wave/orchestrator.md in full — it is your complete role manual. Follow it verbatim.
Argument: the wave manifest file path (e.g. $wave docs/dev/waves/my-wave/wave.md or $wave ./wave.md).
Skill("wave-build", ...) → spawn a Codex Teams child agent: Agent(wave-build, "Pipeline: {name}. Task manifest: docs/dev/builds/{name}/0-task.md. [Wave: {wave-name}]")Skill("professor", ...) → spawn Agent(professor, "...") for refinement, or refine inline if the wave file is already structured.claude/agents/gitter.md as your git protocol manual.git add docs/ and commit the wave dir + its build dirs into git history (docs(${name}): archive wave + builds), then mkdir -p tmp/dev/archive/waves tmp/dev/archive/builds, move the build dirs to tmp/dev/archive/builds/ and the wave dir to tmp/dev/archive/waves/{name}, and commit the removals. Do NOT push — remote publication requires a separate explicit user request such as /git push.