From 64d9f3d49ec04c30d60e57df39225808c2dbfae3 Mon Sep 17 00:00:00 2001 From: Matt Pocock Date: Wed, 1 Jul 2026 10:41:51 +0100 Subject: [PATCH] Add Task ticket type to decision-mapping skill MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Some blockers are neither a decision, a prototype, nor research — just literal manual work (moving data, signing up for a service, provisioning access) that must happen before discussion can move forward. Co-Authored-By: Claude Opus 4.8 --- .changeset/decision-mapping-task-type.md | 5 +++++ skills/in-progress/decision-mapping/SKILL.md | 7 +++---- 2 files changed, 8 insertions(+), 4 deletions(-) create mode 100644 .changeset/decision-mapping-task-type.md diff --git a/.changeset/decision-mapping-task-type.md b/.changeset/decision-mapping-task-type.md new file mode 100644 index 0000000..db333f1 --- /dev/null +++ b/.changeset/decision-mapping-task-type.md @@ -0,0 +1,5 @@ +--- +"mattpocock-skills": minor +--- + +Add a fourth **Task** ticket type to the **`decision-mapping`** skill. Some blockers are neither a decision, a prototype, nor research — just literal manual work that has to happen before the discussion can move forward (moving data, signing up for a third-party service, provisioning access). The agent automates it where it can, otherwise hands the human a precise checklist, and records any resulting facts later tickets depend on. diff --git a/skills/in-progress/decision-mapping/SKILL.md b/skills/in-progress/decision-mapping/SKILL.md index e5dacaf..cc89297 100644 --- a/skills/in-progress/decision-mapping/SKILL.md +++ b/skills/in-progress/decision-mapping/SKILL.md @@ -23,7 +23,7 @@ terse enough to stay token-efficient, and unique within the map. Blocked by: , Status: open | in-progress | resolved -Type: Research | Prototype | Grilling +Type: Research | Prototype | Grilling | Task ### Question @@ -44,13 +44,12 @@ Each ticket must be sized to one 100K token agent session. ## Ticket Types -There are three types of tickets: +There are four 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**: 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. +- **Task**: Literal manual work that must be done before the discussion can move forward — nothing to decide, prototype, or research. Moving data from one place to another, signing up for a third-party service, provisioning access. The agent automates it where it can; otherwise it hands the human a precise checklist to do by hand. Resolved when the work is done; the answer records what was done and any resulting facts (credentials location, new URLs, row counts) later tickets depend on. ## Fog of war