From 09a72ba465bc1d347a0358af049a7f27cd04ff31 Mon Sep 17 00:00:00 2001 From: Matt Pocock Date: Thu, 2 Jul 2026 11:07:27 +0100 Subject: [PATCH] refactor(to-tickets): prune no-ops from the two-readings intro Co-Authored-By: Claude Opus 4.8 (1M context) --- skills/engineering/to-tickets/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skills/engineering/to-tickets/SKILL.md b/skills/engineering/to-tickets/SKILL.md index a26adbe..7246e7b 100644 --- a/skills/engineering/to-tickets/SKILL.md +++ b/skills/engineering/to-tickets/SKILL.md @@ -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.