edkuksa/skills
1
0
Fork 0
mirror of https://github.com/mattpocock/skills.git synced 2026-07-29 02:52:42 +07:00
Code Issues Packages Projects Releases Wiki Activity

refactor(to-tickets): prune no-ops from the two-readings intro

Browse Source 
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Matt Pocock
2026-07-08 14:18:36 +01:00
co-authored by Claude Opus 4.8
parent 386d4ff719
commit 09a72ba465
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skills/engineering/to-tickets/SKILL.md
+1 -1
View File
@@ -8,7 +8,7 @@ disable-model-invocation: true
Break a plan, spec, or conversation into a set of **tickets** — tracer-bullet vertical slices, each declaring the tickets that **block** it.
The blocking edges are the whole point. They make one artifact read two ways: on a **local file** they're written as text and you work it top-to-bottom by hand; on a **real tracker** they're native blocking links, so any agent can grab a ticket whose blockers are all done — the **frontier** — and several can run at once. The edges live in the ticket either way; the medium only decides whether anything acts on them in parallel. You are producing the artifact, not deciding how it's run.
The blocking edges make one set of tickets read two ways. On a **local file** they're written as text — work them top-to-bottom by hand. On a **real tracker** they're native blocking links, so any ticket whose blockers are done is on the **frontier**, and several agents can work it at once. The medium only decides whether the edges are acted on in parallel; you produce the artifact, not the run.
The issue tracker and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.