status-update
/status-update
Pisze aktualizację statusu, raport projektu lub podsumowanie awarii, które zespół czyta szybko, także na podstawie notatek.
- Autor
- jelvodev ↗
- Repozytorium
- yaap ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Pisze aktualizację statusu, raport projektu lub podsumowanie awarii, które zespół czyta szybko, także na podstawie notatek.
Oryginalny opis (EN)
Write a status update, project report, incident summary or FAQ that a team or stakeholders read quickly. Use it whenever the user asks for a weekly update, a progress report, an outage summary, a change announcement or answers to recurring questions, even when they just paste notes.
Jak działa
- 1. Settle the frame
- 2. Write it in its shape
- 3. General rules for any update
- 4. Check before handing it over
Podgląd SKILL.md
--- name: status-update description: Write a status update, project report, incident summary or FAQ that a team or stakeholders read quickly. Use it whenever the user asks for a weekly update, a progress report, an outage summary, a change announcement or answers to recurring questions, even when they just paste notes. license: Apache-2.0 metadata: sources: anthropic-skills/skills/internal-comms --- # Status updates and summaries People read updates in passing. They look for three things: is it fine, what changed, and do I need to do anything. Give them those first, in a fixed shape, with facts instead of adjectives. ## 1. Settle the frame - **Kind.** A status update, an incident summary, FAQ answers, or another message (an announcement, a change notice). Pick the shape below; for anything else, use the general rules at the end. - **Reader.** Who reads it and how much they know. A team needs detail; leadership needs the outcome and the ask. - **Period.** The dates or the event it covers. - **Material.** Use what the user gives you: notes, commits (`git_diff`, the log), issue lists, attachments, earlier updates. Ask for what is missing rather than inventing it; never fill a gap with a plausible number. ## 2. Write it in its shape ### Status update ``` <Project or team>, <period> Status: <on track | at risk | off track>, <one sentence why> Done - <outcome, with a number or link where there is one> Next - <what comes next, with an owner and date where it matters> Needs attention - <blocker, risk or decision needed, and from whom; or "nothing"> ``` - Three to five bullets per part at most. Group small items into one. - Write outcomes, not activity: "the export runs in 2 minutes instead of 20", not "worked on export performance". - "At risk" and "off track" always name what would bring it back and who must act. - Keep the same shape week after week, so readers can compare. ### Incident summary ``` <Title>, <date> Impact: <who or what was affected, how badly, for how long> Status: <resolved | mitigated | ongoing> Timeline (<time zone>) - <time>: <what happened or was done> Cause: <the root cause, or what is known so far> Fix: <what stopped it, and what makes it hold> Follow-up - <action, owner, date> ``` - State the impact in the reader's terms (users who could not log in, orders delayed), with numbers. - Blameless: describe what the system and process allowed, not who made the mistake. - Keep "known" and "suspected" apart. An unconfirmed cause is labelled as such. ### FAQ answers ``` Q: <the question as people ask it, one sentence> A: <the answer in one to three sentences> (<source>) ``` - Collect the questions from the material; merge ones that ask the same thing. - Order by how many people it affects, not by when it was asked. - Base each answer on a source the reader can open, and link it. When the answer is not settled, say so and who decides. ## 3. General rules for any update - The most important line comes first; a reader may stop after it. - Short sentences, active voice, no hype. "Shipped" and "slipped" are both fine words. - Numbers over adjectives; a link over a paraphrase. - Every request names who must act and by when. - Match the tone the user's organisation uses when the user shows an earlier example; otherwise plain and neutral. ## 4. Check before handing it over - Read it as the busiest reader: could they act on the first three lines alone? - Check every number, date and name against the material. Mark anything you could not check. - Cut what the reader does not need; link to the detail instead. Give the user the text ready to paste, and list separately anything you assumed or could not check. Adapted from the `internal-comms` skill of anthropics/skills under the Apache License 2.0: rewritten, its company-specific formats and tools left out, and the status, incident and FAQ shapes written new.
Pliki w paczce (2)
- LICENSE.txt 11 KB
- SKILL.md 4 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · jelvodev/yaap | 100 | MIT |
| caidanw/skills | 96 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki df55a394eac4 (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
- 100report-progress
Pisze raport z postępu według szablonu statusu lub szablonu projektu, gdy ktoś prosi o aktualizację. - 100draft-project-update
Przygotowuje status projektu lub zbiorczy raport wielu projektów dla zespołu, kierownictwa lub klienta, z ryzykami i prośbami o decyzje. - 100program-status-report
Pisze tygodniowy lub dwutygodniowy raport statusu programu dla interesariuszy, z oceną RAG, blokerami i decyzjami do podjęcia. - 100pm-weekly-update
Generuje tygodniowe lub miesięczne raporty statusu z lokalnych danych PM, w tym z notatek ze spotkań, zgłoszeń i decyzji, także w formie maila. - 100stakeholder-update
Pisze krótką aktualizację dla interesariuszy na podstawie trackera i decyzji, zaczynając od tego, co czytelnik musi zrobić. - 86status-report
Przygotowuje raport statusu lub podsumowanie tygodnia, zapisuje go w docs/status i publikuje, bez wklejania w czat.