decision-mapping
Installation
SKILL.md
Decision Mapping
Purpose
Chart the way through an effort too big and foggy for one session. The output is decisions, not deliverables: a shared map of decision tickets that shrinks the fog until the route to the destination is clear — then it hands off; it does not build.
Concepts
- Destination: what reaching the end looks like — a spec to hand off, a decision to lock, or a change to make. Named first; it fixes the scope.
- Map: a single canonical artifact (an issue on the tracker, or a Markdown file) holding the destination, notes, and an index of decisions so far. The map is an index, not a store — a decision lives in exactly one place, its ticket.
- Ticket: one decision or investigation, sized to one session, with blocking edges to the tickets that gate it. Refer to tickets by name, never bare numbers, in anything a human reads.
- Frontier: the open, unblocked, unclaimed tickets — what can be worked now.
- Fog: in-scope questions you can sense but cannot yet state precisely. Write them loosely under "Not yet specified"; they graduate into tickets as the frontier advances. The test: ticket when the question is already sharp, fog when it is not.
- Out of scope: work ruled beyond the destination. Not fog — it never graduates.
Workflow
Charting (first session):