To Tickets

Break a plan, spec, or conversation into a set of tickets: tracer-bullet vertical slices, each declaring the tickets that block it.

The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run /setup-matt-pocock-skills.

Process

1. Gather context

Work from whatever is already in the conversation context. If the user passes a reference (a spec path, an issue number or URL) as an argument, fetch it and read its full body and comments.

2. Explore the codebase (conditional)

Explore when a ticket's area is unfamiliar to a fresh implementer, or when a ticket sits near the smart-zone edge; skip it only when you already know the area and the ticket is small. The output of exploring is the orientation each ticket carries (stable anchors in its Orientation section) so a fresh agent does not have to re-explore — see the smart-zone block below.

Understand the current state of the code, use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.

Look for opportunities to prefactor the code to make the implementation easier. "Make the change easy, then make the easy change."