arda/skills
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Keep Prototype name; move Notes block to end of map

Browse source 
- Revert Sketch back to Prototype to mesh with the /prototype skill and
  existing vocabulary, keeping the generalized function-first definition.
- Move the `## Notes` block from the top of the map to the end.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt Pocock 2026-06-30 18:40:52 +01:00
parent 3dc6800550
commit 79a5c9cc55
1 changed files with 7 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

12
skills/in-progress/decision-mapping/SKILL.md
View file

@ -4,7 +4,7 @@ description: Turn a loose idea into a sequenced map of investigation tickets, th
disable-model-invocation: true
---
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 sketching, research or grilling. The map is domain-agnostic: it plans engineering work, course content, or anything else that fits the same shape.
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 grilling. The map is domain-agnostic: it plans engineering work, course content, or anything else that fits the same shape.
## The Decision Map
@ -12,8 +12,6 @@ The decision map is a single compact Markdown file, one per planning effort, git
Assets created during tickets should be linked to from the map, not duplicated within it.
The map opens with an optional `## Notes` block: part declaration (the **domain**, and which skills every session should `consult`), part freeform preference dump — whatever standing context the planning surfaces. It rides into every session with the map, so **every session honors it**: consult the skills it names, respect its preferences. Notes accrue as they emerge; never manufacture them.
### Structure
Entries ("tickets"), each its own section keyed by a short dash-case slug that
@ -25,7 +23,7 @@ terse enough to stay token-efficient, and unique within the map.
Blocked by: <slug>, <slug>
Status: open | in-progress | resolved
Type: Research | Sketch | Grilling
Type: Research | Prototype | Grilling
### Question
@ -49,7 +47,7 @@ Each ticket must be sized to one 100K token agent session.
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.
- **Sketch**: Raise the fidelity of the discussion by making a cheap, rough, concrete artifact to react to — an outline, a rough take, a stub, or UI/logic code via the /prototype skill. Creates the sketch as an asset. Use this when "how should it look" or "how should it behave" is the key question.
- **Prototype**: Raise the fidelity of the discussion by making a cheap, rough, concrete artifact to react to — an outline, a rough take, a stub, or UI/logic code via the /prototype skill. Creates the prototype as an asset. Use this when "how should it look" or "how should it behave" is the key question.
- **Grilling**: Conversation with the agent. Uses the /grilling and /domain-modeling skills. Asks one question at a time. The default case.
Validation isn't a fourth type — it's the thread running through all three.
@ -105,3 +103,7 @@ End every session by clearing the context and opening one or more fresh sessions
> ```
**No open tickets remain.** The fog is pushed back far enough that the path to the finish line is clear — the map is done. (The initial grilling may also surface no fog at all, in which case there was never a map to build.) Recommend implementing directly, or using `/to-prd` to schedule a multi-session implementation.
## Notes
The map ends with an optional `## Notes` block: part declaration (the **domain**, and which skills every session should `consult`), part freeform preference dump — whatever standing context the planning surfaces. It rides into every session with the map, so **every session honors it**: consult the skills it names, respect its preferences. Notes accrue as they emerge; never manufacture them.