Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Planowanie

status

/status

Pokazuje, na czym stoi repozytorium, co jest otwarte i zablokowane, i przyjmuje odpowiedzi na decyzje.

Licencja
MIT
Ostatnia zmiana repozytorium
26.10.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 26.10.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, na czym stoi repozytorium, co jest otwarte i zablokowane, i przyjmuje odpowiedzi na decyzje.

Wyzwalacze z opisu

where are wewhatwhat do you need from me; says who they asked or who answered (emailed legalDana replied1 -> yes, 2 -> bSHOP-4 -> b
Oryginalny opis (EN)

Where things stand for this repository, and the one way to change it. Use when the user asks "where are we", "what's next", "what do you need from me", "what's open", "what's blocked", "what's urgent"; says who they asked or who answered ("I asked Dana", "emailed legal", "Dana replied"); answers decisions with "1 -> yes, 2 -> b" or "SHOP-4 -> b" (-> answers); says "SHOP-12 is urgent", "agree SHOP-35", "update the status", "mark it done", "we agreed", "show me the board", "put this repo on the board", "/status". Runs the status CLI against STATUS.md on the repository's default branch; it never

Jak działa

  1. 1. Where state lives
  2. 2. A repository that is not on the board yet
  3. 3. The user asks where things stand
  4. 4. The user answers decisions
  5. 5. The user says they asked someone
  6. 6. The card lifecycle (v2)
  7. 7. Rules
Sekcje z nagłówków SKILL.md, w oryginale · 137 linii, 1 443 słów
Podgląd SKILL.md
---
name: status
description: Where things stand for this repository, and the one way to change it. Use when the user asks "where are we", "what's next", "what do you need from me", "what's open", "what's blocked", "what's urgent"; says who they asked or who answered ("I asked Dana", "emailed legal", "Dana replied"); answers decisions with "1 -> yes, 2 -> b" or "SHOP-4 -> b" (-> answers); says "SHOP-12 is urgent", "agree SHOP-35", "update the status", "mark it done", "we agreed", "show me the board", "put this repo on the board", "/status". Runs the status CLI against STATUS.md on the repository's default branch; it never edits that file by hand.
allowed-tools: Bash(status *), Bash(node ${CLAUDE_PLUGIN_ROOT}/bin/status.mjs *)
---

# status

Every command below is `status <verb> …`: the plugin puts `status` on the Bash tool's PATH. Type it that way
(it runs without a permission prompt while this skill is active). If the shell answers "status: command not
found", use `node ${CLAUDE_PLUGIN_ROOT}/bin/status.mjs <verb> …` instead. Run it from inside the repository's
checkout, any worktree; from anywhere else add `--repo SHOP` (the key, the initiative or the slug).

`/status` runs `show`; `/status all` runs `all`; `/status doctor` runs `doctor`.

The examples below use a made-up repository with the key SHOP and two people, Dana and Legal. Use the real
board's key and the names in its Who and With cells.

## 1. Where state lives

- The board is `STATUS.md` on the repository's default branch (`main`) on GitHub. The CLI reads it from there and
  changes it one card at a time; every change is one commit straight to `main`.
- Never edit `STATUS.md` in a working tree: not with the Edit tool, not in a worktree, not in a PR. A checkout's copy
  is stale the moment the CLI writes; it is never the source.
- Never write status into memory files: no PR numbers, no "live since", no done lists, no open-item counts, no
  hashes. Memory holds how-to knowledge; the board holds state.
- Hashes and counts do not go into the board either; the CLI refuses them.
- **Two contracts.** A `status/v2` board (front matter `contract: status/v2`) is a kanban: every card has a
  permanent id (`SHOP-12`) and sits in a column: You decide, Waiting on others, Backlog, To do, In progress, In
  review, Done, Parked, Settled. A `status/v1` board has numbered rows instead. The CLI says which verbs fit: a
  verb of the other contract exits 2 and names the right call. Migrating a v1 board is the user's call:
  `status migrate` shows the plan; never run `--apply` without their go-ahead in their own words.
- The CLI records the user (the `"me": true` entry of `~/.config/status-board/people.json`) as the one who agreed,
  decided or parked. Do not pass `--by` unless the user says someone else made the call.

## 2. A repository that is not on the board yet

Trigger: "put this repo on the board", "set up status here", "track this repo". The session brief is silent in a
repository the registry does not know.

```
status init
```

Without `--key` it stops and suggests one: ask the user for the key (2-6 capitals: the prefix of every card id,
SHOP-1, SHOP-2…) and a short name, then run the dry run with them and show the plan:
`… init --key SHOP --name "Acme Shop"`. Only on their go: the same call with `--apply`. It creates an empty
STATUS.md on the default branch (one commit, never over an existing file) and registers the repo in
`~/.config/status-board/repos.json`. Then help fill the Backlog with `add` (section 6).

## 3. The user asks where things stand

Trigger: "where are we", "what's next", "what do you need from me", "what's open", "what's urgent", "/status".

```
status show
```

Print the output inside a fenced code block, as it comes, then stop. Do not summarise it a second time, do not
start on anything it lists. On a v2 board the cards carry ids: list them by id and never re-number them. On a v1
board print the "You decide" rows numbered, exactly as the CLI numbers them, so the user can answer "1 -> yes".
`show --all` expands the collapsed groups and Settled. One card in full: `status card SHOP-4`.

Across every repository: `status all`. Hygiene and staleness: `status doctor`.

"Show me the board", "open the board": the board is a pane only the user can open. Tell them to type `/board`.
If they say it is out of date, rebuild its file with `status board` (read-only; every write refreshes it on its
own). The pane never changes STATUS.md: its Answer buttons put "SHOP-4 (…) -> b" into the prompt, and the answer
then comes to you as in section 4.

## 4. The user answers decisions

Trigger: "SHOP-4 -> b", "1 -> yes, 2 -> b", "-> answers", "go with the second option for 4".

On a v2 board a bare number N means SHOP-N only when the last board listing in this chat carried ids; otherwise ask
which card. Echo `SHOP-4 (<title>) -> b` before writing, then one call per answer, in the user's words:

```
status decide SHOP-4 --answer "block gift cards until the terms are approved" --said "4 -> a"
```

(on a v1 board: `status decide 4 --answer "…"`). Then put the user's words into the right DECISIONS file through
the normal PR flow (repos.json lists the repository's `decisions` files) and pass `--record <path#id>` next time.
Without `--record` the CLI prints a reminder; keep it in your report.

- Wrong card answered: `… reopen SHOP-4 --why "<why>"`.
- "later", "park it", "not now": `… park SHOP-8` (v2). On a v1 board: `… park "<what>" --from decide:3` (the section
  prefix matters there: Next rows carry the same numbers, so a bare `3` is refused).
- A decision needs someone else first: `… move SHOP-4 waiting --who Dana` (v2), or
  `… add waiting --who Dana --ask "<ask> (reg:X)" --since today`.

## 5. The user says they asked someone

Trigger: "I asked Dana about SHOP-21 today", "emailed legal about C5 yesterday", "chased ops on F1".

```
status asked Dana SHOP-21 --on today --via email --said "<their words>"
```

One card per call; on a card that waits on two people only that person's entry changes. Who, card and channel
come from the user's words; the date is today unless they give one (`--on "21 Oct"`). A ref works too
(`reg:B3`). Mark `asked` only from the user's own words: never because you drafted the message, never because a PR
mentions it.

## 6. The card lifecycle (v2)

- Propose: `… add "<what>" --ref reg:F3` lands in Backlog as `proposed`. Follow-on work: `--from SHOP-1`.
  A dated reminder: `--due "2 Jan 2027"`.
- The user agrees: `… agree SHOP-35 --said "<their words>"` moves Backlog to To do (`--to progress` when they say
  start now; `--first` puts it at the top). Their direct request for new work: `… add "<what>" --to progress --said "…"`.
- Start: `… move SHOP-35 progress`. PR opened: `… move SHOP-35 review --pr 20`, and write `Card: SHOP-35` in the PR
  body (`Card: none` when no card applies).
- Finished (merged, and live where that matters): `… done SHOP-35 --pr 20 --evidence "<what shows it>"`. Finished
  work that never had a card: `… add "<outcome>" --to done --pr 19`.
- Blocked on someone: `… move SHOP-35 waiting --who Dana`; they answered: `… replied SHOP-21 --outcome "<what>"`.
- The user says it is urgent: `… urgent SHOP-12 --said "<their words>"`; no longer: `… urgent SHOP-12 --clear`.
  Overdue cards and asks whose chase is due show as urgent on their own.
- Not wanted after all: `… drop SHOP-37 --why "<why>"`.
- A decision, blocker or evidence worth keeping: `… card note SHOP-21 "<text>"`. Options for a decision:
  `… card set SHOP-4 --body-file <file>` with `**Options**` lines `- a) …` and a `**Recommend**` line, drafted
  by you, decided by the user.
- The user went through the board with you: `… review`.

On a v1 board the same events use the v1 verbs: `status done reg:F4 --outcome "…" --pr 19`,
`status replied reg:B2 --outcome "…"`, `status next add "<what>" --ref reg:F3`, `… next agree 2`,
`… now "<what>" --state "…"`, `status add waiting --who Dana --ask "<ask> (reg:X)" --since today`,
`status add decision "<question> (reg:X)" --with Dana --since today`, `… add followup --when "…" --what "…"`,
`status review`.

## 7. Rules

- One call per event. Report each write in one line: the CLI prints the commit subject and the row before and
  after; relay that, nothing more.
- `agree`, `asked`, `decide` and `urgent` only from the user's own words, always with `--said`. Claude proposes
  (`add` lands in Backlog); the user agrees and decides.
- Never type hashes or counts into STATUS.md; pins live in the repository.
- The brief printed at session start is a pointer to the board, not a substitute for reading `CLAUDE.md`.
- `--dry-run` on any write shows the change and the commit message without writing.
- If a write ends with "board change not saved", run `… flush` once; if that fails too, say so and stop.
- If the CLI exits 2 (usage, or a verb of the other contract) read its message and make the call it names; if it
  exits 1 with "no matching card", run `show` and name the card by its id.

Wersje

RepozytoriumWynikLicencja
Ta strona · MichaelFu1998-create/claude-status-board100MIT
finolabs/finolabs-vibecode100MIT
jeremylongshore/tons-of-skills-marketplace100MIT
rossoctl/context-guru100Apache-2.0
crisandrews/clawcode100MIT
wrg32786/aigent-os100MIT
zereight/gitlab-mcp100MIT
emaballarin/ccplugins100MIT
wookiya1364/scv-claude-code100MIT

Migawka bazy z 13.11.2026 · wersja paczki e8204493aad9 (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

  • 90pc-status
    Pokazuje postęp wszystkich planów w repozytorium lub jednego z nich i podaje, co uruchomić dalej.
  • 100plan-board
    Pokazuje plan, roadmapę lub status jako czytelny diagram tekstowy z decyzjami na górze i opcjonalnie publikuje interaktywną tablicę, na której można zatwierdzać, odrzucać i komentować decyzje.
  • 90board
    Pokazuje status tablicy DevFlow: epiki, zadania, statusy i otwarte ustalenia, a także pozwala zarządzać zadaniami.
  • 100pm
    Prowadzi publiczną tablicę adopcji .pm: pokazuje status, tworzy strumienie pracy, zbiera notatki w inboxie, awansuje je do kamieni milowych, dodaje zadania, zamyka zrobione, parkuje zablokowane i porzuca zbędne.
  • 100session-status
    Pokazuje, co zostało w sesji: pracę w toku, nieodpowiedziane pytania, nierozstrzygnięte decyzje, blokery i proponowany tytuł.
  • 100planr
    Prowadzi pracę produktową jako graf zadań w Markdownie: pokazuje gotowe i zablokowane zadania oraz bezpiecznie zmienia statusy.

Uwagi i zgłoszenia

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