From 5d78bd0903420f97c791f834201e550c765699f8 Mon Sep 17 00:00:00 2001 From: Matt Pocock Date: Thu, 25 Jun 2026 12:48:23 +0100 Subject: [PATCH] fix: correct spelling of 'domain-modeling' in decision-mapping documentation --- skills/in-progress/decision-mapping/SKILL.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/skills/in-progress/decision-mapping/SKILL.md b/skills/in-progress/decision-mapping/SKILL.md index 1f4a683..e463507 100644 --- a/skills/in-progress/decision-mapping/SKILL.md +++ b/skills/in-progress/decision-mapping/SKILL.md @@ -39,7 +39,7 @@ 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. -- **Grilling**: Conversation with the agent. Uses the /grilling and /domain-modelling skills. Asks one question at a time. The default case. +- **Grilling**: Conversation with the agent. Uses the /grilling and /domain-modeling skills. Asks one question at a time. The default case. ## Fog of war @@ -55,7 +55,7 @@ There are two ways this skill can be invoked: **bootstrap** and **resume**. User invokes with a loose idea. -1. Run a /grilling + /domain-modelling session to surface the open decisions. Ask one question at a time. +1. Run a /grilling + /domain-modeling session to surface the open decisions. Ask one question at a time. 2. Write a new decision map — mostly fog, frontier identified, trivially-decidable entries resolved inline. 3. Stop. Map-building is one session's work; do not also resolve tickets. @@ -64,7 +64,7 @@ User invokes with a loose idea. User invokes with a path to an existing map and a ticket number. 1. Load the **whole map** as context. -2. Run a session to resolve the ticket, invoking skills as needed. If in doubt, use `/grilling` and `/domain-modelling`. +2. Run a session to resolve the ticket, invoking skills as needed. If in doubt, use `/grilling` and `/domain-modeling`. 3. Record what the session resolved in the ticket's body. 4. Add newly-discovered tickets (with correct `blocked_by` edges). 5. Stop.