Przejdź do treści
Biblioteka skilli
AI i agenci · Analiza

wave-status

/wave-status

Pokazuje tylko do odczytu status potoku wave-triage, wave-plan i wave-run: postęp funkcji, powód ostatniego zatrzymania i kolejne kroki.

Repozytorium
wave-method ↗
Licencja
MIT
Ostatnia zmiana repozytorium
09.11.2026

Ocena i bezpieczeństwo

100/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść35 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
1
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 09.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.

Co robi i kiedy

Pokazuje tylko do odczytu status potoku wave-triage, wave-plan i wave-run: postęp funkcji, powód ostatniego zatrzymania i kolejne kroki.

Wyzwalacze z opisu

что с планамипочему волна встала
Oryginalny opis (EN)

Read-only status of the wave-triage → wave-plan → wave-run pipeline. For every plan in plans/ (not archived) — or one given plan folder — lead with each feature's status, task progress and what it waits for, then show which wave is running, why the last wave stopped, ready features waiting for the user's review (their essence, how to test them, branch, merge command), leftover worktrees and branches, unplanned index parts, and the next command. Never writes, commits or deletes anything. Use when the user runs "/wave-status [<plan folder>]", asks "что с планами", "почему волна встала", "почему

Jak działa

  1. Hard rule
  2. Input
  3. What to read
  4. Report
  5. Next-command rules
Sekcje z nagłówków SKILL.md, w oryginale · 119 linii, 1 251 słów
Podgląd SKILL.md
---
name: wave-status
description: Read-only status of the wave-triage → wave-plan → wave-run pipeline. For every plan in plans/ (not archived) — or one given plan folder — lead with each feature's status, task progress and what it waits for, then show which wave is running, why the last wave stopped, ready features waiting for the user's review (their essence, how to test them, branch, merge command), leftover worktrees and branches, unplanned index parts, and the next command. Never writes, commits or deletes anything. Use when the user runs "/wave-status [<plan folder>]", asks "что с планами", "почему волна встала", "почему фича не смержилась", or before starting a wave. Recommended model: low complexity (Haiku 5.5 or any stronger model).
---

# wave-status — read-only pipeline status

Language: talk to the user in the language of their messages; write everything into the repository in English,
always (`wave-plan/layout.md`, "Language"). Start and end time of the run: `wave-plan/layout.md`, "Run times".

Skill paths such as `wave-plan/layout.md` are relative to the wave skills folder, the parent of this skill's
folder (`wave-plan/layout.md`, "Skill paths").

## Hard rule

Read only. No file edits, no commits, no worktree or branch deletion, no builds, no tests. Cleanup is only
suggested as commands for the user in the report; never execute those commands.

## Input

The argument is an optional plan folder. Without it, inspect every plan folder under `plans/` except
`plans/archive/`, plus every index (`plans/<date>-<topic>/index.md`).

## What to read

Read only the following, according to `layout.md`, "Who reads what":

- Each plan's `README.md` from the tracking branch when `plan/<plan>` exists
  (`git show plan/<plan>:<plan folder>/README.md`), otherwise from the main checkout. Use its Features columns
  `| ID | Slug | Title | P | Tasks (wave) | Done when | Status | Waiting for | Branch | Merged |` and Waves
  columns `| Wave | File | Tasks | Status |`, and its Tasks columns `| ID | Slug | Feature | Wave | Complexity | Status |`.
- Each plan's `problems.md`: entry headers only (`**[I<n> · …] essence**`).
- The wave file of a wave that is 🔄, ❌ or ⚠️: only its "Execution" section, for the last
  `Stop <code>: … — next: …` or `Waiting: task mode <IDs> — next: …` line.
- For each `👀 review` feature: its review brief `reviews/<feature>.md`. Only when it has none: the README's
  "User problems" lines of its P and its "How to try" line, its commit subjects
  (`git log --oneline --no-merges <main>..<branch>`), and the "Execution" section of the wave file of its last wave
  (the last wave in its "Tasks (wave)" cell), for what was checked by hand.
- Each index's "Parts" table.
- `git worktree list --porcelain`, `git branch --list "plan/*" "feat/*" "task/*"`,
  `git status --porcelain --untracked-files=no` of the main checkout, and
  `git branch --merged <main> "feat/*"`.

Do not read solutions, task prompts, other sections of wave files, history or archived plans. The tracking
branch is authoritative for plan status; read its problem headers and Execution sections there as well when
it exists. Use `git show plan/<plan>:<plan folder>/<file>` and retain only the allowed portions.

## Report

For each plan, report the following in order. Keep a blank line before and after every table. Feature status
comes first: the user reads it before anything about waves.

- Header: plan folder, slug, tracking branch present or absent.
- `Features:` one line with the count per status, for example `5 — 2 ✅ merged · 1 👀 review · 1 🔄 · 1 ⚠️`
  (omit statuses with a count of 0).
- The feature table below, one row per feature of the README's Features table, in its order, using the README's
  `Status`, `Waiting for`, `Branch` and `Merged` values. `Branch` is the feature branch `feat/<plan>/<feature>`
  (`—` when it does not exist yet); for a `👀 review` feature it is the branch the user reviews. Show an old
  `✅ ready` as `👀 review` (`layout.md`, "Statuses"). `Tasks` is `<done>/<total>`: tasks of the feature with
  status ✅, over its tasks that are not ➖ (`—` when none). Add the failing task IDs after it for ⚠️ and ❌ tasks
  (`2/4 · ⚠️ B`).
- `Waves:` the wave statuses on one line (`1 ✅ · 2 🔄 since <date time> · 3 ⬜`); the 🔄 wave is the running one.
  `none running` when no wave is 🔄.
- `Ready for review:` the review block of `layout.md`, "Feature review", for every `👀 review` feature, with its
  `Merge:` line, from its brief; never shortened to the title and branch, and nothing else about the feature.
  For `main-dirty` add its reason (`not on <main>`, `staged changes`, or the overlapping paths); the three read-only
  commands of `layout.md`, "Main readiness", may be run to find it. A feature without a brief (a plan run by an
  older `wave-run`) gets the same block, built from what "What to read" lists: the essence from its title, P lines
  and commit subjects; "How to test" from its "How to try" line, otherwise from what the Execution section says was
  checked by hand, as feature-specific steps; otherwise `not recorded — <Done when>`. Do not say where the text
  came from.
- `Merged, not recorded:` a feature branch merged into `<main>` whose row is not `✅ merged` (the user merged it);
  the next `/wave-run <plan folder>` · `$wave-run <plan folder>` records it.
- `Last stop:` the last `Stop <code>: … — next: …` line, or `Waiting: task mode <IDs> — next: …`.
- `Inconsistencies:` a ⚠️/❌ item that names no open entry; an open entry whose items are all ✅ or ➖ (the
  status check of `layout.md`, "Statuses").
  May run the script read-only on a plan folder of the tracking branch's worktree; otherwise check by reading.
- `Leftovers:` task branches or worktrees of waves that are not 🔄; feature worktrees of merged features; a
  tracking branch of an archived plan. Give a suggested cleanup command for each, as described below.
- `Next:` one command, following the first applicable next-command rule. For task mode, include each required
  task-mode command.

| Feature | Status | Tasks | Waiting for | Branch | Merged |
|---|---|---|---|---|---|
| F1 <Title> | <README status> | <done>/<total> | <README Waiting for> | <feature branch> | <README Merged> |

Then report each index's parts without a plan folder, whether their "Plan when" condition is met, and their
`/wave-plan <index> part <K>` · `$wave-plan <index> part <K>` commands.

### Suggested commands

The commands in this subsection are suggestions for the user's report only. Do not execute them.

- Leftover worktree: `git worktree remove <absolute worktree path>`.
- Leftover task, feature or tracking branch: `git branch -d <branch>`; suggest removing an attached worktree
  first. Do not suggest forced deletion.
- A ready feature: `/wave-run <plan folder> merge <F-ID>` · `$wave-run <plan folder> merge <F-ID>`, for use after
  the user has reviewed it; for `main-dirty`, once the main checkout is ready (`layout.md`, "Main readiness").
- A finished plan that has not been archived: suggest the applicable `git mv` command from
  `layout.md`, "Archive". For an index part, the whole index folder is eligible only when every part is merged.

## Next-command rules

Use the first rule that applies:

1. A wave is 🔄 waiting for task mode: give its task-mode commands
   `/wave-run <plan folder> <N> task <ID>` · `$wave-run <plan folder> <N> task <ID>`.
   Otherwise a 🔄 wave means `wait: wave N is running`.
2. The last wave is ❌: use the `next:` command of its stop line.
3. Open entries not marked `→ task …`: `/wave-plan <plan folder>` · `$wave-plan <plan folder>`.
4. A feature `👀 review`: "review `<branch>`, then" and its merge command (see "Suggested commands"). If rule 5 also
   applies, give its command on a second line: a wave waits for a review only when its `Depends on:` names the
   feature (`wave-run` then stops `feature-unmerged`).
5. The first ⬜ wave whose earlier waves are ✅, ⚠️ or ➖:
   `/wave-run <plan folder> <N>` · `$wave-run <plan folder> <N>`.
6. Every feature merged: `finished; archived by the last wave-run`, or the suggested archive command if the
   plan is not archived.

The report ends with the `Started: … · Finished: …` line (`layout.md`, "Run times").

Write commands in both forms (`layout.md`, "Commands"). Running-wave locks and task-mode
waiting follow `layout.md`, "Running waves".

Wersje

W bazie nie ma innych skilli o nazwie wave-status.

Migawka bazy z 13.11.2026 · wersja paczki 15b985291e20 (skrót SHA-256 całej paczki)

Pobrania w ostatnich 30 dniach: 0 · ranking

Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.

Podobne skille

  • 100wave-triage
    Dzieli listę problemów na części, zadaje pytania wyjaśniające raz, ocenia trudność i tworzy indeks zadań.
  • 100wave-plan
    Zamienia listę problemów i funkcji w plan wdrożenia dla równoległych subagentów, z falami zadań i gotowymi promptami.
  • 100wave-executor
    Wykonuje plan falowy: uruchamia równoległych agentów dla każdej fali, pilnuje bramek scalania i buduje samodzielne prompty z wierszy dokumentu fal przygotowanego przez wave-execution-planner.
  • 100run-wave
    Uruchamia falę elementów pracy MCP według wygenerowanego planu: ustala front gotowych elementów, wyprowadza etapy z ich schematów, otwiera przebieg na serwerze i wykonuje plan przez Workflow lub bezpośrednie wywołania agentów.
  • 100build-feature
    Prowadzi fazę budowy zatwierdzonego planu falami, czeka na scalenie PR i na końcu otwiera PR do gałęzi bazowej.
  • 95wave-conductor
    Prowadzi plan kodowania przez Wave Conductor, pilnuje wykonania do końca i informuje właściciela o ważnych zmianach.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.