wave-start
Start a new wave. Default runs the canonical v2 framework (17 phases + conditional [DR] for UI waves at 1.5 + optional [CR] gate at 3.5, max 19). Pass --demo…
Save wave state to disk so an auto-compact, session crash, or laptop battery death doesn't kill the run. Run this between phases or before any long operation.
> /plugin marketplace add Harshvardhan86/claude-wave-plugin > /plugin install claude-wave-plugin@claude-wave-plugin
How it fires
How this command gets triggered: by you, by Claude, or both.
/wave-checkpointContext preview
What this command does when you run it.
Save wave state to disk so an auto-compact, session crash, or laptop battery death doesn't kill the run. Run this between phases or before any long operation.
description: Save wave state to disk so an auto-compact, session crash, or laptop battery death doesn't kill the run. Run this between phases or before any long operation. allowed-tools: "Bash(mkdir:*), Bash(date:*), Bash(git:*)"
The `PreCompact` hook now writes a checkpoint automatically before compaction during an active wave. This command is the manual form: use it between phases or before a long operation. Compaction itself cannot be blocked; resume from the checkpoint in a fresh terminal.
Save a wave checkpoint to `.wave/checkpoints/<timestamp>.md` containing:
1. **Wave goal** — the original feature description from `/wave-start`. 2. **Phase reached** — which of AC / DR / RED / GREEN / TEET is currently in flight. 3. **Last verified evidence** — paste the most recent screenshot path, test output, or computed-style assertion result. NOT "tsc passes". Real evidence only. 4. **Open questions** — anything the user still has to decide. 5. **Resume instructions** — exact commands and prompts a fresh session would need to pick up where this one left off.
If `.wave/` does not exist, create it. In a git repository, add `.wave/` to `.git/info/exclude` if the entry is missing, following `wave-init.sh`. Resolve the local exclude file with `git rev-parse --git-path info/exclude` when the git directory is elsewhere.
After writing the checkpoint, print the file path and the resume command to the user. Do not commit checkpoints — they're local recovery state, not source.
Run Claude Code like an engineering org. Wave-based execution with dedicated sub-agents per phase, computed-style visual verification, no "tsc passes" lies.
Repo: Harshvardhan86/claude-wave-plugin
Start a new wave. Default runs the canonical v2 framework (17 phases + conditional [DR] for UI waves at 1.5 + optional [CR] gate at 3.5, max 19). Pass --demo…