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

decision-map

/decision-map

Mapuje decyzje w mglistej pracy przed napisaniem plastrów budowy: nowy prymityw, karta kamienia milowego albo integracja, której nikt nie opisze naraz.

Repozytorium
skills ↗
Licencja
MIT
Ostatnia zmiana repozytorium
19.10.2026

Ocena i bezpieczeństwo

90/ 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ść25 / 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
3
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
1
Przestarzałość

Brak sygnałów. Repozytorium zmienione 19.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

Mapuje decyzje w mglistej pracy przed napisaniem plastrów budowy: nowy prymityw, karta kamienia milowego albo integracja, której nikt nie opisze naraz.

Oryginalny opis (EN)

Chart or work a decision map for genuinely foggy work before any build slice is written: a new primitive, a milestone charter, an integration nobody can spec in one sitting. Use when asked to chart a decision map, work a map ticket, or plan a decision-heavy effort whose open questions gate each other.

Jak działa

  1. Mode 1: charting a new map (invoked with a scope or destination)
  2. Mode 2: working a ticket (invoked with a map ticket)
  3. Done when (checkable: verify each line before reporting complete)
  4. Hard guardrails
  5. Attribution
Sekcje z nagłówków SKILL.md, w oryginale · 38 linii, 700 słów
Podgląd SKILL.md
---
name: decision-map
description: "Chart or work a decision map for genuinely foggy work before any build slice is written: a new primitive, a milestone charter, an integration nobody can spec in one sitting. Use when asked to chart a decision map, work a map ticket, or plan a decision-heavy effort whose open questions gate each other."
---

# Decision Map

A decision map turns fog into recorded decisions. It is for work nobody can spec in one sitting, where the open questions gate each other. It produces decisions, not deliverables: once the protocol's map-done condition holds (frontier empty and the Not-yet-specified ledger empty), the scope specs and builds as ordinary tracked work.

You are running a decision-map session. The protocol authority is [references/protocol.md](references/protocol.md). Read it first, whole; this skill only sequences the session. If the consuming repo has a domain-vocabulary or context doc (see its team-workflow binding doc, seeded by the setup skill), load that too and use its terms.

## Mode 1: charting a new map (invoked with a scope or destination)

1. Write the destination paragraph first, one paragraph on what "decided" looks like for this scope, then survey the fog against the current code and docs per the protocol's charting section.
2. Choose the weight by fog density (deep → child gate-decision tickets, resolved most-gating-first; shallow → single-sitting adjudication) and say which you chose and why. When the survey finds no fog, take the early exit: write a normal work-item spec instead and say so.
3. Write the map doc, tracked, at `docs/<scope>-decision-map.md` (or the docs home your binding doc names) with both ledgers (Not yet specified / Out of scope) present, even when empty.
4. Deep weight: file the child tickets on the repo's tracker, attach every one to the parent ticket as a native sub-issue per the protocol's sub-issue section, wire blocking edges between dependent tickets per the protocol's recipe, and post the suggested resolution order (most-gating-first) on the parent ticket.
5. Brief the decider on the map and the first frontier round.

## Mode 2: working a ticket (invoked with a map ticket)

1. Claim the ticket per the repo's claim recipe (the tracker-discipline binding applies unchanged).
2. Run the ticket by its type per the protocol's ticket-type table (for a prototype ticket, call the Skill tool with `prototype`; for a research ticket, call the Skill tool with `research` and follow it).
3. Record the outcome on the ticket, write the one-line verdict back into the map doc, and name any newly unblocked tickets (the frontier moved).

## Done when (checkable: verify each line before reporting complete)

- Charting: the map doc exists tracked in the repo with a destination paragraph, both ledgers, and every surveyed question either ticketed, listed under Not yet specified, or ruled Out of scope with its ruling, no question left unplaced. At deep weight, every filed child ticket is a native sub-issue of the parent ticket, or carries the `Part of #<parent-number>` line because `gh` or the tracker could not attach one.
- Working: the ticket carries its recorded outcome, the map doc carries the check-off pointer, and blocking edges/labels reflect the new frontier.
- Map close: the protocol's map-done condition holds, verified against both ledgers → parent ticket closed, build work filed normally.

## Hard guardrails

- Sessions brief decisions; the decider decides. On reaching a decision point, record the recommendation and stop there: the round brief is the deliverable, never the answer.
- Deviations from a recorded decision go back to the decider; carry them as questions in the next round brief, never as reinterpretations inside a build brief.

## Attribution

This skill and its [protocol](references/protocol.md) are adapted from Matt Pocock's [`wayfinder`](https://github.com/mattpocock/skills/tree/main/skills/engineering/wayfinder) (MIT), and follow it closely. The core model is his: the destination named before anything is surveyed, the map as an index whose decisions live on their tickets, decision tickets that produce decisions rather than deliverables, the four ticket types, the fog of war with the Not-yet-specified and Out-of-scope ledgers, the fog-or-ticket test, refer-by-name, the no-fog early exit, native blocking edges rendering the frontier, one ticket per session, and create-then-wire filing. Attaching each child ticket to the parent ticket as a native sub-issue follows his later wayfinder change.

What this repo adds: the weight choice by fog density (deep child tickets vs single-sitting shallow adjudication), the coupling to the binding doc and the named decider, the `gate-decision` label riding the pack's tracker discipline, the edge-vs-`blocked`-label division of labor, the map-done condition checked against both ledgers, and the sub-issue recipe and its fallbacks.
Pliki w paczce (3)
  • SKILL.md 5 KB
  • agents/openai.yaml 1 KB
  • references/protocol.md 9 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · timharris707/skills90MIT
mathews-tom/armory100MIT
timharris707/skills90MIT

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

  • 100flow-next-chart
    Rozbija zbyt duży i niejasny pomysł na mapę decyzji, rozstrzyga jedną decyzję naraz i przygotowuje podsumowanie do specyfikacji.
  • 100flow-next-chart
    Prowadzi odkrywanie mapy decyzji dla jednego zbyt dużego, niejasnego pomysłu przed capture: jedna decyzja na wywołanie i brief do dalszej pracy.
  • 96milestone-review
    Przygotowuje pełny przegląd postępu kamienia milowego: kompletność funkcji, wskaźniki jakości, ryzyka i rekomendację: start albo wstrzymanie.
  • 90kata-plan-phase
    Planuje fazę pracy w Kata: dzieli cel kamienia milowego na wykonalne zadania.
  • 100grill-me
    Przeprowadza wywiad przed nową pracą i zapisuje uzgodniony brief budowy dla nowego projektu, kamienia milowego, aplikacji, skilla, automatyzacji, dokumentu lub projektu graficznego.
  • 100milestoneplan
    Pokazuje plan wykonania kamienia milowego jako tabelę z numerem issue, opisem, złożonością, zależnościami, modelem, wysiłkiem i planem, tylko do odczytu, bez edycji i uruchamiania.

Uwagi i zgłoszenia

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