Matt PocockandClaude Opus 4.8
386d4ff719
Executes the `unify-to-tickets` decision (personal-wiki #23), reworking this PR from "add /to-plan" into the full planning-skills unification. - Rename /to-prd → /to-spec. "spec" is now the single through-line term (the skill still opens with "you may know this document as a PRD" for discoverability). - Merge /to-plan + /to-issues into one /to-tickets skill; delete /to-issues. /to-tickets emits a set of tickets, each declaring its blocking edges — one medium-agnostic artifact that reads as a sequential plan (local `tickets.md`, edges as text) or a parallelizable DAG (real tracker, native blocking links). The edges live in the ticket either way; the medium only decides whether anything acts on them in parallel. - ask-matt now routes idea → /to-spec → /to-tickets → /implement. - Sweep every cross-reference (docs pages, chain diagrams, CONTEXT.md, ADRs, .agents, setup templates) to the new names and vocabulary. - Rewrite the changeset to describe the unification. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.3 KiB
Matt Pocock Skills
A collection of agent skills (slash commands and behaviors) loaded by Claude Code. Skills are organized into buckets and consumed by per-repo configuration emitted by /setup-matt-pocock-skills.
Language
Issue tracker:
The tool that hosts a repo's issues — GitHub Issues, Linear, a local .scratch/ markdown convention, or similar. Skills like to-tickets, to-spec, triage, and qa read from and write to it.
Avoid: backlog manager, backlog backend, issue host
Issue:
A single tracked unit of work inside an Issue tracker — a bug, task, spec, or slice produced by to-tickets.
Avoid: ticket (use only when quoting external systems that call them tickets)
Triage role:
A canonical state-machine label applied to an Issue during triage (e.g. needs-triage, ready-for-afk). Each role maps to a real label string in the Issue tracker via docs/agents/triage-labels.md.
Relationships
- An Issue tracker holds many Issues
- An Issue carries one Triage role at a time
Flagged ambiguities
- "backlog" was previously used to mean both the tool hosting issues and the body of work inside it — resolved: the tool is the Issue tracker; "backlog" is no longer used as a domain term.
- "backlog backend" / "backlog manager" — resolved: collapsed into Issue tracker.