# Waves

> Router for the waves work framework. Use when starting work in a waves workspace/repo, when the user types /waves with no specific sub-skill, or asks 'how do we work here'. Routes to waves-init (workspace setup), waves-plan (task breakdown), waves-run (parallel execution via agent teams or subagents), waves-status (coordinator blurb), platform-guide (third-party dashboard how-tos).

- Skill: `asunalabs/waves` (Agent Skill)
- Install (CLI): `npx skillmds@latest add asunalabs/waves`
- Raw SKILL.md: https://api.skillmd.com/api/skills/asunalabs/waves/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: asunalabs (https://skillmd.com/u/asunalabs)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/asunalabs/waves

---


# waves — work framework router

## Preamble (run first)

```bash
"${CLAUDE_PLUGIN_ROOT}/scripts/waves-detect"
```

Read the output before deciding anything: it tells you the workspace root, the
repos present (branch, worktree vs clone, which have CLAUDE.md/rules), whether
agent teams are enabled, and the config (coordinator, blurb language, task cap,
execution backend, model policy).

## Routing

| Intent | Skill |
|---|---|
| New workspace / "init this task" / repo has no agent rules | `waves-init` |
| Turn a goal, spec, or clip into an executable plan; break work into tasks | `waves-plan` |
| Execute a plan / "run the next wave" / fan out agents or teammates | `waves-run` |
| "Send a status" / wave closed / session ending | `waves-status` |
| "How do I do X in the Shopify/Meta/Forge/… dashboard" | `platform-guide` |

If the request is a video/voice review clip, run the `clip-to-plan` plugin first,
then hand its output to `waves-plan` to convert into the master-plan format.

## Standing context (applies to every route)

Read `${CLAUDE_PLUGIN_ROOT}/references/conventions.md` for the process rules.
Three rules dominate everything:

1. **Never silently default on a real fork.** Every decision that changes what
   gets built is presented to the user as a decision brief —
   `${CLAUDE_PLUGIN_ROOT}/references/decision-briefs.md` has the format
   (D-numbered, ELI10 + stakes, one recommended option, honest tradeoffs).
2. **Repo rules override framework rules** inside that repo. Before touching
   code in any repo, Read its `CLAUDE.md` + relevant `.claude/rules/*.md`.
3. **Verification is per-task and live** — green suites alone never count
   (conventions §5).