decision-mappinglisted

This skill is invoked when a loose idea requires more than one agent session to turn into a plan. It creates a stateful decision map in a markdown file, and drives the user through a sequence of tickets to resolve the open questions - which may require either prototyping, research or discussion. ## The Decision Map The decision map is a single compact Markdown file, one per planning effort, git-tracked alongside the project. It is the canonical artifact — the **whole map is loaded as context into every session**, so it must stay compact. Assets created during tickets should be linked to from the map, not duplicated within it. ### Structure Numbered entries ("tickets"), each its own section keyed by its number: ```markdown ## #1: Relational Or Non-Relational Database? Blocked by: #<ticket-number>, #<ticket-number> Type: Research | Prototype | Grilling ### Question <question-here> ### Answer <answer-here> ``` Each ticket must be sized to one 100K token agent session. ## Ticket Types There are three types of tickets: - **Research**: Reading documentation, third-party API's, or local resources like knowledge bases. Creates a markdown summary as an asset. Use this when knowledge outside the current working directory is required. - **Prototype**: Writing UI or logic code to test a hypothesis, or to explore a design space. Uses the /prototype skill. Creates a prototype as an asset. Use this when "how should it look" or "how should it behave" is the key question. - **G