chore: version skills

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

mattpocock-skills@1.1.0

Minor Changes

• #406 930a450 Thanks @mattpocock! - Bring the ask-matt router up to date with the full skill set. It now maps five skills it was missing: tdd (woven into the main flow as the red-green engine implement drives), diagnosing-bugs (a new "Something's broken" on-ramp — there was previously no route for a bug), domain-modeling and codebase-design (a new "Vocabulary underneath" section), and grilling (the shared interview primitive). prototype is fleshed out as a standalone and the description broadens from "user-invoked skills" to "the skills". A maintenance rule is added to CLAUDE.md so any future skill add/rename/remove or flow change triggers an ask-matt re-check, beside the existing docs-page re-sync rule.

• #405 14c13c5 Thanks @mattpocock! - Rename the in-progress review skill to code-review and promote it from in-progress/ to the engineering/ bucket. It now ships in the plugin, is listed in the top-level and Engineering READMEs (Model-invoked), and has a human-facing docs page at docs/engineering/code-review.md. The /implement skill and docs now point at /code-review.

• #401 64d9f3d Thanks @mattpocock! - Add a fourth Task ticket type to the decision-mapping skill. Some blockers are neither a decision, a prototype, nor research — just literal manual work that has to happen before the discussion can move forward (moving data, signing up for a third-party service, provisioning access). The agent automates it where it can, otherwise hands the human a precise checklist, and records any resulting facts later tickets depend on.

• #433 e1c025e Thanks @mattpocock! - Add a confirmation gate to grilling: the agent won't enact the plan until you confirm the shared understanding has been reached, turning the skill's existing "shared understanding" completion criterion into an explicit stop-gate. The description also recruits the pretrained grill leading word ("Grill the user relentlessly") to sharpen invocation, and the docs page is re-synced with the new gate behaviour.

• 850873c Thanks @mattpocock! - Make the prototype skill model-invoked, so the agent can reach for it autonomously (and other skills can too). Its description is rewritten around the leading word prototype — throwaway code that answers a design question — with one trigger per branch (state/logic sanity-check, or UI exploration).

• #409 0d74d01 Thanks @mattpocock! - Add the research skill — a small, model-invoked skill that spins up a background agent to investigate a question against primary sources (official docs, source code, specs, first-party APIs), then leaves a single cited Markdown file wherever the repo keeps such notes. It's delegable reading legwork: you keep working while it reads, and get back a document to grill, plan, or design against. Listed in the top-level and Engineering READMEs (Model-invoked), added to .claude-plugin/plugin.json, given a docs page at docs/engineering/research.md, and routed as a Standalone in ask-matt.

• #436 6f9e995 Thanks @mattpocock! - Change wayfinder's claim mechanism from a label to an assignee.

  A session now claims a ticket by assigning it to the dev driving the map, rather than setting a wayfinder:claimed label. The assignee is the claim — an open, unassigned ticket is unclaimed — which reads more naturally in GitHub's own UI and frees the label vocabulary to wayfinder:<type> alone. The claim leading word and its "first, before any work" rationale are unchanged; only the physical expression moved.

• #413 5c3c49d Thanks @mattpocock! - Make wayfinder collaborative by moving the map off a local Markdown file and onto the repo's issue tracker.

  The map is now a single wayfinder:map issue whose tickets are its child issues — one shared URL the whole team can watch and comment on. Blocking, claiming (wayfinder:claimed), and the frontier query all use native tracker semantics, so a session loads the map at low resolution (Notes + one context pointer per closed ticket + Fog prose) and zooms into individual tickets on demand, instead of loading the whole map every time.

  Wayfinder stays tracker-agnostic: the per-tracker mechanics live behind a pointer in docs/agents/issue-tracker.md, so setup-matt-pocock-skills now seeds a "Wayfinding operations" section for GitHub, GitLab, and local-markdown. Absent that doc, Wayfinder defaults to local-markdown.

• #419 9272935 Thanks @mattpocock! - Make wayfinder's no-duplication contract explicit: the map is an index, not a store.

  Adopting "index" as the leading word for the map's role fixes two duplication risks. The map now states up front that a decision lives in exactly one place — its ticket — so it only ever gists and links, never restates the answer (previously this rule was implied inside an HTML comment in the map-body template). And graduating fog into a ticket now clears the graduated patch from the Fog, so a suspected question can't linger in both places at once.

• #428 8cc3328 Thanks @mattpocock! - Reframe wayfinder's description around the work it's for: planning a huge chunk of work, more than one agent session can hold.

  The description does the skill's invocation work, so it now leads with the trigger that actually reaches for Wayfinder — a big effort you need to break down — instead of the softer "chart a route through a foggy problem". The skill body and fog-of-war mechanic are unchanged.

• #412 4027ea6 Thanks @mattpocock! - Rename the decision-mapping skill to wayfinder, invoked as /wayfinder.

  "Decision map" was jargony and inaccurate — only one of the skill's four ticket types (Grilling) is actually a decision. The reframe charts a route through a foggy problem, resolving investigation tickets one at a time until the way to the goal is clear. This makes one coherent leading-word frame (fog of war / frontier / the map) instead of mixing an invented term on top of it.

  Also a pruning pass: unified node→ticket, bound "the frontier" to the unblocked tickets, dropped the duplicated "one question at a time" (owned by /grilling), and trimmed intro no-ops.

Patch Changes

• #394 7a4c756 Thanks @mattpocock! - Give the in-progress code-review skill an always-on Fowler smell baseline on its Standards axis. A curated ~12 high-signal "Bad Smells in Code" (Mysterious Name, Duplicated Code, Feature Envy, Data Clumps, Primitive Obsession, Repeated Switches, Shotgun Surgery, Divergent Change, Speculative Generality, Message Chains, Middle Man, Refused Bequest) are inlined into SKILL.md as a fixed baseline alongside whatever the repo documents — not a new third axis. Two binding rules keep it safe: a documented repo standard overrides the baseline, and every smell is reported as a judgement call, never a hard violation.

• #393 e81f976 Thanks @mattpocock! - Reshape the tdd skill into reference-only. The red → green → refactor loop is anchored by leading words the model already holds, so the step-by-step Workflow was largely restating the loop and duplicating the horizontal-slicing anti-pattern. Dropped the Workflow and per-cycle checklist; folded their one durable idea — vertical slices / tracer bullets — into the Anti-patterns section and a short Rules-of-the-loop list. Introduced seam as the leading word for where tests go, collapsing the old Philosophy "public interfaces" prose and the Planning "confirm interface / behaviors" handshake into one rule: test only at pre-agreed seams, confirmed with the user before any test is written.

  Also dropped the refactor stage — TDD is now red → green, not red → green → refactor. Refactoring belongs to the review stage, not the implementation loop, so the refactor rule and refactoring.md were removed (its home is the review skill).

• 43ea088 Thanks @mattpocock! - Add the tautological test anti-pattern to the tdd skill. Tests whose assertion is recomputed the way the code computes it pass by construction and give zero confidence — distinct from the implementation-coupling anti-pattern already covered. Added as a peer at the same three sites: a Philosophy principle (expected values must come from an independent source of truth), a per-cycle checklist gate, and a BAD/GOOD example pair in tests.md.

• e00eadb Thanks @mattpocock! - Extend the triage skill to triage external pull requests, treating a PR as an issue with attached code that runs through the same roles and state machine. PRs flow inline alongside issues (gated by a per-repo setup toggle), discovery surfaces only external PRs, the bug-only "reproduce" step is generalized into a single "verify the claim" step, and a redundancy check resolves already-implemented requests to wontfix without polluting the out-of-scope knowledge base. setup-matt-pocock-skills gains the PRs-as-a-request-surface toggle for GitHub/GitLab.

• #435 b289481 Thanks @mattpocock! - Sharpen Wayfinder's blocking rule to prefer the tracker's native dependency relationship, and update the GitHub and GitLab issue-tracker templates to match.

  Native blocking is essential rather than cosmetic: it renders the frontier visually in the tracker's own UI, so the human sees what's takeable at a glance without opening the map. wayfinder's SKILL.md now states that preference and rationale; the GitHub template spells out the native issue-dependencies recipe (gh api .../dependencies/blocked_by, frontier query on issue_dependencies_summary.blocked_by), and the GitLab template names the native /blocked_by blocking link (Premium/Ultimate) with the body-convention fallback. Both keep the body fallback for trackers that lack native blocking.