From d29732e49f60a71e2036471c8eaa31631bf5151c Mon Sep 17 00:00:00 2001 From: Matt Pocock Date: Thu, 2 Jul 2026 11:09:24 +0100 Subject: [PATCH] refactor(to-tickets): cut the two-readings explainer from SKILL.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It documented what the skill does rather than steering the agent — the publish mechanics it described are already Step 5's instructions, and the conceptual framing already lives in ask-matt and the docs page. Co-Authored-By: Claude Opus 4.8 (1M context) --- skills/engineering/to-tickets/SKILL.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/skills/engineering/to-tickets/SKILL.md b/skills/engineering/to-tickets/SKILL.md index 7246e7b..dceaa73 100644 --- a/skills/engineering/to-tickets/SKILL.md +++ b/skills/engineering/to-tickets/SKILL.md @@ -8,8 +8,6 @@ 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 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. ## Process