People kept reading a wayfinder ticket as an ordinary implementation ticket — a slice of a build to execute — when wayfinder uses them as decision tickets: questions whose resolution is a decision. Introduce "decision ticket" as a light leading word: the skill description and its opening line name it (and say what makes it one), and the ask-matt / engineering README blurbs and the docs page match, while "ticket" stays the everyday word once the term is established. Record "Decision ticket" in CONTEXT.md so the "avoid: ticket" domain rule no longer contradicts wayfinder's deliberate use of the word. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.8 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, or for a Decision ticket — see below)
Decision ticket:
A wayfinder unit — a child Issue of a wayfinder:map holding a question whose resolution is a decision, not a slice of a build to execute. The decision qualifier is what keeps it distinct from an implementation ticket; wayfinder introduces the term, then uses "ticket".
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
- A Decision ticket is an Issue (a child of a
wayfinder:map)
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.