What wave-orchestrator runs automatically, and when. A hook is a command Claude Code fires at a fixed moment, without you asking for it.
Claude Code
> /plugin marketplace add Harshvardhan86/claude-wave-plugin> /plugin install wave-orchestrator@wave-orchestrator
Cursor
Cursor also runs Claude Code hooks from .claude/settings.json, so copy these hooks there to use them in Cursor.
What fires, and when
PreToolUse
^Agent$"${CLAUDE_PLUGIN_ROOT}"/scripts/hooks/pre-agent.sh^(Edit|Write|NotebookEdit|MultiEdit)$"${CLAUDE_PLUGIN_ROOT}"/scripts/hooks/pre-edit.sh^Read$"${CLAUDE_PLUGIN_ROOT}"/scripts/hooks/pre-read.sh^Bash$"${CLAUDE_PLUGIN_ROOT}"/scripts/hooks/pre-bash.sh^Bash$"${CLAUDE_PLUGIN_ROOT}"/scripts/hooks/pre-commit-guard.sh^Monitor$"${CLAUDE_PLUGIN_ROOT}"/scripts/hooks/pre-monitor.shPostToolUse
^Agent$"${CLAUDE_PLUGIN_ROOT}"/scripts/hooks/post-agent.sh^Bash$"${CLAUDE_PLUGIN_ROOT}"/scripts/hooks/post-bash.shSubagentStop
"${CLAUDE_PLUGIN_ROOT}"/scripts/hooks/subagent-stop.shPreCompact
"${CLAUDE_PLUGIN_ROOT}"/scripts/hooks/pre-compact.shSessionStart
Fires once when a session begins, and again after a context compaction. It is where a plugin sets up its environment, or restores state the compaction dropped.
startup|resume|clear|compact"${CLAUDE_PLUGIN_ROOT}"/scripts/hooks/session-start.shStop
"${CLAUDE_PLUGIN_ROOT}"/scripts/hooks/stop.shUserPromptSubmit
Fires before Claude sees each prompt you send. A plugin can use it to inject context, so the same instruction reaches the model every turn instead of only at session start.
"${CLAUDE_PLUGIN_ROOT}"/scripts/hooks/user-prompt.shIn the plugin's words
How wave-orchestrator describes its own hook set.
Wave hook enforcement: phase order and hand-off artifacts, per-role model routing, orchestrator-only editing/reading/bash in the main session, a commit-message guard, a token ledger and a scorecard pointer. Every command below is silent (exit 0, no output) whenever no wave is
Run your coding agent like an engineering org. Wave-based execution with dedicated sub-agents per phase, computed-style visual verification, no "tsc passes" lies.
Stars on GitHub
A development methodology for coding agents that makes the agent brainstorm before building, follow plans, run parallel work and finish branches in a disciplined way. You get fewer skipped steps and more consistent results from your coding assistant.
@obraA Claude Code plugin with skills for auditing a whole repo, reviewing a change, listing deferred shortcut comments, and showing measured savings and a quick command reference.
@dietrichgebertWalks a software change from a written spec through design, testing, code review, CI/CD, and release, applying the matching engineering skill at each stage. Useful for developers using Claude Code on full development workflows.
@addyosmaniPersistent file-based planning for AI coding agents on long-running, multi-step tasks. It keeps task_plan.md, findings.md and progress.md on disk, so work can resume after /clear or context compaction.
@othmanadiA spec-driven development workflow for Claude Code that guides a project through planning, phases, milestone audits and fixes. Includes skills to generate tests from UAT criteria and to audit completed work.
@open-gsdChinese-language skill pack for Claude Code that adds workflow guidance for brainstorming, TDD, debugging, and code review, plus Chinese conventions for commits, documentation, and domestic Git platforms like Gitee and Coding.net.
@jnmetacodeGives Claude Code semantic search, dependency graph and architecture context over a codebase, so an AI assistant can explore and understand a project's code. Includes skills for indexing a project and managing its file watching.
@giancarloerraA lightweight code search engine that uses AST-based semantic search with local embeddings and incremental indexing. It helps Claude Code users find code faster and more efficiently.
@cocoindex-io