Add Task ticket type to decision-mapping skill
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 <noreply@anthropic.com>
This commit is contained in:
parent
7c1d609ce2
commit
64d9f3d49e
2 changed files with 8 additions and 4 deletions
5
.changeset/decision-mapping-task-type.md
Normal file
5
.changeset/decision-mapping-task-type.md
Normal file
|
|
@ -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.
|
||||
Loading…
Add table
Add a link
Reference in a new issue