decision-record
/decision-record
Zapisuje krótko decyzję dotyczącą dostawcy, projektu lub polityki: kontekst, opcje, osobę decydującą, dowody, to, co ją zmieni, i datę przeglądu.
- Autor
- SHOTClubhouse ↗
- Repozytorium
- shotos ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 10.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 4
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 10.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
Zapisuje krótko decyzję dotyczącą dostawcy, projektu lub polityki: kontekst, opcje, osobę decydującą, dowody, to, co ją zmieni, i datę przeglądu.
Oryginalny opis (EN)
Writes a short record of a decision: context, options, decision, who decided, evidence, what would change it and review date. Use when a supplier, design, policy or scale-pivot-stop call needs recording, or someone asks \"why did we do this?\
Jak działa
- Context and handoff
- When not to use this
- Steps
- Output
- Checks
Podgląd SKILL.md
--- name: decision-record description: "Writes a short record of a decision: context, options, decision, who decided, evidence, what would change it and review date. Use when a supplier, design, policy or scale-pivot-stop call needs recording, or someone asks \"why did we do this?\"" --- # Write a decision record Capture a decision while the reasons are fresh, in one page, so that later readers can see what was chosen, why, and what would reopen it. Stage: any, most often Track. Rules: 4 Claim only what you can show, 1 Stop at the boundaries. ## Context and handoff - **Business question:** what did we decide, who decided, and what would reopen it? - **Use this when** a supplier, design, policy or scale-pivot-stop call needs recording, or someone asks "why did we do this?". It records a call made; it does not make it, and it is not an experiment result (`experiment-plan`) or a route (`route-the-work`). - **Minimum context:** the original decision or the options, constraints, who had authority, the decision date and the evidence. - **Decision boundary:** only the authorised person or body decides. A draft, recommendation or discussion note confers no authority. - **Next step:** the named follow-up owner acts; `progress-wrap-up` communicates impact when needed. Keep the record in the existing project log and link to the evidence. ## When not to use this Skip it for a trivial or easily reversed choice that no one will ask about. Do not use it to make the decision: the agent records a decision the authorised person or body has made or drafts options for them to choose between. ## Steps 1. **Name the decider.** Record the person with authority, or the formally authorised body if the decision belongs to it. For a body, cite its mandate and name the person accountable for following up. Advisory support and an individual vote do not establish a decision. If authority is unclear, keep it open. 2. **State the context.** Two to five sentences: the situation, the constraint, the deadline and what happens if nothing is decided. Link to the problem statement or evidence pack rather than repeating it. 3. **List the options.** At least two real options, plus "do nothing" where it is a real choice. For each give what it costs, what it gains, the main risk and how reversible it is. Include the option that was rejected first and why. 4. **Record the decision.** One sentence in plain words, with the controlling record, date and scope. Include conditions and exclusions that affect what can happen next. If the decider has not decided yet, write "Draft, awaiting the decider" and give a recommendation labelled as such. 5. **Attach the evidence.** List the facts that carried the decision, each with a source and date. Mark which are measured, which are inferred and which are opinion. Keep opinions that disagreed with the outcome and say who held them. 6. **Say what would change it.** Name at least one observable trigger: a number crossing a line, a cost rise, a supplier change, a failed test. This is the contrary case for the decision. 7. **Set a review date.** Pick a date or an event after which someone looks again. Say who reviews. 8. **Note what this supersedes or depends on.** Link earlier records. Mark the older one "superseded by" with the new one's number. 9. **Check authority.** Name the next action, its owner and what proves completion. Carry exact authorisation from the controlling record and list any further approval or condition separately. A recommendation, discussion note or drafted record cannot confer authority. Use the [committee decision example](committee-example.md) to check the difference. ## Output Use [template.md](template.md). Save in the project's decisions folder, numbered, for example `decisions/0007-choose-booking-supplier.md`. Never edit an accepted record to change the outcome; write a new one that supersedes it. ## Checks - The decider is a named authorised person or body. For a body, the record cites its authority and names the person following up. - At least two options with a downside for the chosen one. - Evidence items have sources and are labelled measured, inferred or opinion. - A change trigger and a review date are present. - The recorded decision, action approval and execution status each match their own evidence.
Pliki w paczce (4)
- README.md 3 KB
- SKILL.md 4 KB
- committee-example.md 1 KB
- template.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · SHOTClubhouse/shotos | 100 | MIT |
| event4u-app/agent-config | 100 | MIT |
| Fili999/ai-hub | 100 | MIT |
| scratchpad-sh/skills | 100 | MIT |
| JordzPope/claude-skills-hiring-interviews | 100 | MIT |
| donald-ada/workinggenius | 100 | MIT |
| vickydotbat/vicky-skills | 90 | MIT |
| bmad-code-org/BMAD-METHOD | 80 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 26caf16bacbb (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
- 90create-decision-log
Zapisuje decyzję produktową lub inżynierską z pełnym kontekstem, na prośbę o zalogowanie decyzji lub udokumentowanie, dlaczego coś postanowiono. - 100pm-decision-document
Tworzy rekordy decyzji produktowych w stylu ADR: kontekst, rozważone opcje, kompromisy, podjęta decyzja i konsekwencje, z wymogiem uwzględnienia alternatyw. - 100adr
Pisze lub ocenia rekord decyzji architektonicznej dla serwisu: kontekst, kryteria, opcje, decyzję i konsekwencje. - 86log-decision
Zapisuje decyzję albo przyjęte ryzyko w dzienniku decyzji, gdy właściciel lub zespół coś ustali. - 100adr
Tworzy rekord decyzji MADR 4 z transkrypcji spotkania, notatek albo czatu, zachowując odrzucone opcje i powody. - 100pivot-decision
Strukturyzuje decyzję o zmianie kierunku, kontynuacji lub zakończeniu według frameworku pivotu Erica Riesa z Lean Startup, porównując metryki z pierwotnymi hipotezami i oceniając opcje na danych.