How do I install the Waves skill?

Run npx skillmds@latest add asunalabs/waves in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Waves safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Waves?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Waves free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

asunalabs (@asunalabs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Waves by asunalabs — Agent Skill

Name: Waves
Author: asunalabs

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).

asunalabs Updated Sep 22, 2026

File contents

waves — work framework router

Preamble (run first)

"${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:

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).
Repo rules override framework rules inside that repo. Before touching code in any repo, Read its CLAUDE.md + relevant .claude/rules/*.md.
Verification is per-task and live — green suites alone never count (conventions §5).

---name: wavesdescription: 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).---# 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, therepos present (branch, worktree vs clone, which have CLAUDE.md/rules), whetheragent 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).

Frequently asked questions