# Waves Status

> Generate a coordinator status blurb (language + audience from config) from the master plan and git state — what shipped, what's next, impediments, decisions needed. Use at wave boundaries, session end, or when the user asks to 'send a status' / 'blurb'.

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

---


# waves-status — coordinator status blurb

## Preamble (run first)

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

## Gather (don't ask the user what happened — derive it)

- `plans/00-master.md`: task rows whose status changed since the last blurb (the
  `## Status` section shows the last one), wave closures, open questions.
- `git log --oneline` since the last blurb across workspace repos; PRs opened.
- Anything explicitly marked "flag in blurb" in plans or notes.

## Compose

Language: `blurb_language` from config. Audience: `coordinator_name` from config.
Style — non-negotiable:

- **Compact and forwardable as-is**: no preamble, no agent-speak, no markdown
  headers. Short lines or tight bullets.
- One sentence per item: what was done (deliverable-level, not code-level), what's
  next, impediments.
- **Decisions needed are explicit**, each with the proposed default so the
  coordinator can answer with a yes ("I propose X — ok?"). Decisions the *user*
  must make don't go in the blurb — present those directly as decision briefs
  (`${CLAUDE_PLUGIN_ROOT}/references/decision-briefs.md`).
- Link PRs/branches/docs where the work lives; mention verification only as
  confidence ("E2E-tested in the browser"), not process detail.
- Early rather than late; the coordinator must never have to chase.

## Deliver

Show the blurb to the user for forwarding (they send it — you don't). Then append a
dated entry to `## Status` in `plans/00-master.md` recording that the blurb was
prepared and what it covered. If open questions were flagged, mark them
"awaiting answer" in the open-questions section rather than assuming answers.