c66bdeeee0
Delete the four skills in deprecated/ — design-an-interface, qa, request-refactor-plan, ubiquitous-language — each already absorbed by a promoted skill. The bucket itself stays, now empty: a retired skill is deleted, and the changeset that removes it names its replacement. Delete edit-article and obsidian-vault along with the personal/ bucket. obsidian-vault hardcoded a path to Matt's own vault and was model-invocable, so any skills.sh user could have had it fire on them. None of the six was in the plugin, but skills.sh serves every SKILL.md in the repo, so all six were installable — hence the changeset. Reframe in-progress/ from scratchpad to beta channel: public on purpose, feedback wanted, not in the plugin, and installable one skill at a time through skills.sh. Nothing there is deleted or graduated. Drop qa from the two live docs that cited it as an issue-tracker skill. ADR 0002 is left untouched — it records reasoning that was true when decided. Resolves mattpocock/personal-wiki#256 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1.7 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, and triage 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.