decision-record
/decision-record
Prowadzi w .genius/DECIDED.md indeks rozstrzygniętych decyzji projektu, po jednej linii na decyzję, wskazującej spór, który ją rozstrzygnął.
- Autor
- donald-ada ↗
- Repozytorium
- workinggenius ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 03.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 03.10.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
Prowadzi w .genius/DECIDED.md indeks rozstrzygniętych decyzji projektu, po jednej linii na decyzję, wskazującej spór, który ją rozstrzygnął.
Oryginalny opis (EN)
Keep the index of the project's settled decisions in .genius/DECIDED.md — one line per decision, pointing at the fight that settled it, earned by one test: would a future stranger re-fight this? Use when such a decision lands, when a design might contradict a settled one, or when another skill needs the index discipline.
Jak działa
- The line
- The test
- The discipline
Podgląd SKILL.md
--- name: decision-record description: "Keep the index of the project's settled decisions in .genius/DECIDED.md — one line per decision, pointing at the fight that settled it, earned by one test: would a future stranger re-fight this? Use when such a decision lands, when a design might contradict a settled one, or when another skill needs the index discipline." --- # The Decision Index A decision is never written twice. The flow already writes every decision at full strength — kill-reasons, the survivor's fight, the user's confirmation — into the work file where it was made. What those records lack is a door: a fresh session judging a new design cannot trawl every done file for the one decision it is about to contradict. The door is `.genius/DECIDED.md` — one line per settled decision, each pointing at the fight that settled it. ## The line ```markdown - **Raw SQL over any ORM** — schema drift burned v1; queries are few and hand-debugged. [The fight](checkout-rework/log/discernment.md#discernment) ``` Verdict in bold, the why in one line, the link relative to `.genius/`. A decision that landed outside the flow — no work file, no battlefield — carries its why in the line itself, one honest sentence rather than a verdict alone. ## The test An index line is earned by one question: **would a future stranger re-fight this?** — propose the killed thing again, redo the settled study, "fix" the deliberate deviation. Most decisions fail it: they bind only their own work. The ones that pass: architectural shape, boundary no-s, deliberate deviations from the obvious path, constraints invisible in the code, rejections that will be re-proposed by someone who wasn't there. And a seam or convention a slice established that later work will build against — close-out asks the test of the contract's established layer first, block by block, because a builder in the next work re-derives whatever no line lets it find. ## The discipline - **Written when the record is finished**, because the line points at a fight, and a fight the work can still reopen or abandon is not yet settled. Tenacity's close-out asks the test of everything the work settled; a standalone `/architect` study writes its line when the design is confirmed; a decision that landed outside the flow writes its line when it lands, because there the line *is* the record. Never a second write-up: the line points, the record carries. - **Read before contradicting, and before introducing.** The index is the ammunition `/discern` and `/architect` load: a design that touches a settled decision either dies of the fight on record or names the decision it overturns and why. It is also where an inventor or a builder looks before introducing a seam or a convention, and reuses the one it finds. - **Overturning moves the line.** A new fight that beats a settled decision rewrites its line — new verdict, new link — and the old record stays as written. The index carries what the project believes now; the files carry how it came to believe it. Not a second place decisions get written — a line that restates the fight will drift from it. Not a diary: a decision that fails the stranger test gets no line, and that is the discipline working.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · donald-ada/workinggenius | 100 | MIT |
| event4u-app/agent-config | 100 | MIT |
| Fili999/ai-hub | 100 | MIT |
| SHOTClubhouse/shotos | 100 | MIT |
| scratchpad-sh/skills | 100 | MIT |
| JordzPope/claude-skills-hiring-interviews | 100 | MIT |
| vickydotbat/vicky-skills | 90 | MIT |
| bmad-code-org/BMAD-METHOD | 80 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki e38d3d4b81df (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
- 100write-adr
Zapisuje ustalony wybór jako ADR, gdy decyzja przeżyje wysiłek, który do niej doprowadził. - 100cover-genius-webhooks
Odbiera i weryfikuje webhooki Cover Genius (XCover) Offers: nasłuch, nagłówek X-Api-Key, błędy 401 oraz zdarzenia ubezpieczeń wbudowanych, jak BOOKING_CREATED, BOOKING_CANCELLED i RENEWAL_DUE. - 100adr
Zapisuje jako ustrukturyzowane ADR decyzje architektoniczne, które już zapadły, gdy wybór między alternatywami został rozstrzygnięty. - 100decision-memory
Ładuje decyzje, które już rządzą pracą w repozytorium z ADR (zwykle docs/adr), porównuje z nimi plan lub diff i zapisuje nową decyzję, a także pomaga ustalić, gdzie rzecz została rozstrzygnięta. - 90record-prose
Określa, jak pisze się dokumenty przepływu pod .genius/, od migawki po linię backlogu, oraz dyscyplinę prozy dla innych skilli. - 90new-adr
Zapisuje istotną decyzję architektoniczną w formacie MADR w docs/adrs i aktualizuje indeks, także przy zastępowaniu wcześniejszej decyzji.