Work Tickets

Run this after /to-tickets has published an approved set of implementation tickets. Act as a stateless coordinator over durable project state: the tracker holds work state, Git holds implementation evidence, and repository docs hold durable knowledge.

The user should normally invoke this skill once. Continue across tickets without routine confirmation until the requested set is complete or a human-judgement boundary is reached.

Reuse the Matt workflow

Read repository instructions first. Reuse the configuration written by /setup-matt-pocock-skills:

• docs/agents/issue-tracker.md is the tracker adapter. Use its fetch, list, comment, label/status, close, and generic dependency primitives, plus any implementation-ticket lifecycle operations.
• docs/agents/triage-labels.md, when present, maps canonical roles such as ready-for-agent to repository vocabulary.
• docs/agents/domain.md is the domain-doc consumer contract. Follow its pointers to relevant CONTEXT.md, CONTEXT-MAP.md, and ADRs; when those artifacts are absent, proceed silently.
• The ticket and linked spec are the implementation contract. Wayfinder maps and decision tickets are historical context loaded only through relevant pointers.

Treat tracker sections scoped to another skill—especially Wayfinding operations—as that skill's lifecycle, not this one's. Reuse a medium primitive such as reading the same native dependency representation that /to-tickets published, but do not inherit map/child updates, claims, answers, or resolution side effects unless the adapter explicitly generalizes them to implementation tickets.

If docs/agents/issue-tracker.md is missing, stop and ask the user to run /setup-matt-pocock-skills. Keep tracker-specific commands in that repository file; do not copy them into this skill.