v1.3.22026-10-29
Patch Changes
- #1194 b645f47 Thanks @mattpocock! - ask-matt now reads a skill's SKILL.md before stating what it does or recommending a step be skipped, instead of trusting its own one-line summaries (#614).
- #1304 5beb35b Thanks @mattpocock! - chief-of-staff now keeps its memory in an LLM wiki (an index.md plus one page per topic, maintained through ingest, query and lint) and writes it as a historical record: every claim is dated, and every claim about code cites the commit it was true at.
- #1208 3da8c01 Thanks @mattpocock! - code-review now searches the repo for standards files and always hands CODING_STANDARDS.md / CONTRIBUTING.md to the Standards sub-agent (#1065), runs both sub-agents in the foreground and uses their returned reports (#1073), and resolves the issue tracker through the provided tracker doc instead of a hard-coded path (#937).
- #1209 f3fc563 Thanks @mattpocock! - diagnosing-bugs Phase 5 now has the agent diff a forced mutation against a pristine copy before trusting the red, so an edit that silently changed nothing can't pass as a failing test (#955).
- #1187 e0efb6e Thanks @mattpocock! - Fixed the GitHub tracker template's external-PR listing, which failed on authorAssociation (#468, thanks @lofi-coding). Re-run /setup-matt-pocock-skills to refresh docs/agents/issue-tracker.md.
- #1169 59db609 Thanks @mattpocock! - The GitHub issue tracker template that setup-matt-pocock-skills writes now tells agents to file issues only into the user's own repo, never into mattpocock/skills, and to check the target repo before the first gh issue create. Agents working in a clone or fork of this repo had filed their specs and tickets here (#541 to #550).
- #1193 95249b0 Thanks @mattpocock! - grilling words each question so "yes" accepts the recommended answer, so agreeing never means answering "no" (#706).
- #1184 4f4e943 Thanks @mattpocock! - handoff now names where the OS temp directory is ($TMPDIR, else /tmp; %TEMP% on Windows), so agents stop guessing (#272).
- #1189 e48341a Thanks @mattpocock! - implement now calls the Skill tool for tdd and code-review instead of bare /skill prose, matching #878.
- #1196 6d6a5b9 Thanks @mattpocock! - implement fetches a passed ticket reference from the issue tracker and states its title before starting, asking when the reference is ambiguous (#700).
- #1228 ed0de59 Thanks @mattpocock! - setup-matt-pocock-skills now wires up a git remote before writing a GitHub/GitLab tracker that nothing can reach (#1201), and offers to git mv a legacy CONTEXT.md / CONTEXT-MAP.md to its GLOSSARY name (#1176). The GitHub template comments before closing (#873), reads a PR's body as well as its comments (#1138), moves Blocking into Conventions with the native gh flags (#855), and names the command that counts open blockers (#1118). The GitLab template lists MRs with -O json and names the frontier query's command (#1143). Re-run /setup-matt-pocock-skills to refresh docs/agents/.
- #1197 5b7cade Thanks @mattpocock! - setup-matt-pocock-skills now creates missing triage labels on GitHub/GitLab (#616), fixes the GitLab template's glab commands (#635), reads GitHub issues with --json so labels and body come through (#733), and names the "Label in our tracker" column in triage-labels.md (#801). Re-run /setup-matt-pocock-skills to refresh docs/agents/.
- #1341 7739eae Thanks @mattpocock! - Skills that dispatch subagents (implement-spec, code-review, codebase-design, improve-codebase-architecture, wayfinder, research, grilling, chief-of-staff) now say to start each one with a fresh context window rather than forking the current conversation, which some harnesses (Codex) do by default and which throws away the clean context a subagent exists for.
- #1192 3f59913 Thanks @mattpocock! - tdd now gives each proposed seam a one-line note on what it catches and what it misses, so choosing between seams is no longer a guess (#607).
- #1183 ad5400b Thanks @mattpocock! - teach quizzes vary which position holds the correct answer ([#611](https://github.com/mattpocock/s
v1.3.12026-10-04
Minor Changes
- #1120 2aecca1 Thanks @mattpocock! - Graduate implement-spec into the Engineering bucket, so it ships in the Claude Code plugin, gets a docs page, and is routed by ask-matt as the parallel alternative to per-ticket implement.
implement-spec (user-invoked) implements a whole spec in one run. It reads the tickets as a task graph, runs implementer subagents in their own worktrees across the ready frontier, and lands everything on one integration branch, closing out with code-review. Ahead of graduating:
- The goal is now the integration branch, not a PR. A draft PR opens only when the issue tracker closes work through PRs or you ask for one, and only after the first merge (a branch with no commits ahead of main can't open one). Without a PR, the tickets are resolved the way the tracker closes work.
- It points at the issue tracker like its siblings, telling you to run /setup-matt-pocock-skills when none has been provided, rather than silently defaulting to gh.
- Each implementer confirms its worktree is based on the integration branch, builds its ticket with tdd, and merges the integration tip into its own branch before reporting done, so each merge is a fast-forward.
- #1120 2aecca1 Thanks @mattpocock! - Graduate pr into the Engineering bucket, so it ships in the Claude Code plugin, gets a docs page, and is routed by ask-matt as the PR-body close-out.
pr (model-invoked) is the shape a pull request body should take: a summary as the smallest visual that makes the change clear (pseudocode, a call tree, a file tree, Mermaid, a diff), before/after evidence that it works, and a merge-danger call (one-way or two-way door, plus blast radius). The Summary visuals are adapted from Dex Horthy's show-me, credited in the skill's CREDITS.md.
- #1120 2aecca1 Thanks @mattpocock! - Graduate retro into the Engineering bucket, so it ships in the Claude Code plugin, gets a docs page, and is routed by ask-matt as the last step of the main flow, after code-review.
retro (user-invoked) looks back at a coding session and suggests changes to the agent's environment rather than the code: navigation pointers, automated checks, coding standards, steering files, tool economy, information access. It classifies each coding-standards finding first: a mechanical violation gets a deterministic check (a linter rule, a pre-commit hook, or a CI job), and CODING_STANDARDS.md is kept for genuine judgement calls. A repo with no guardrail at all is a finding in its own right.
- #1120 daa01d8 Thanks @mattpocock! - Remove the resolving-merge-conflicts skill. It's no longer needed, and nothing replaces it: the agent works through an in-progress merge or rebase conflict without a dedicated skill. It leaves the Claude Code plugin, the README and the ask-matt router. Its docs page at https://aihero.dev/skills-resolving-merge-conflicts stays up, marked archived.
- #1120 006a52b Thanks @mattpocock! - Rename the CONTEXT.md/CONTEXT-MAP.md domain-doc convention to GLOSSARY.md/GLOSSARY-MAP.md everywhere the skills read and write it (domain-modeling, grill-with-docs, improve-codebase-architecture, setup-matt-pocock-skills, triage, tdd, diagnosing-bugs, ask-matt, codebase-design, wait-what, pr), plus the docs pages and this repo's own root glossary.
If you have an existing CONTEXT.md (or CONTEXT-MAP.md) from before this change, git mv it to the new name: the skills only look for GLOSSARY.md/GLOSSARY-MAP.md going forward.
Patch Changes
- #848 f02e2ed Thanks @mattpocock! - domain-modeling: trigger on discussing codebase terminology and on writing or editing a GLOSSARY.md or an ADR directly, replacing the narrower "pin down domain terminology or a ubiquitous language" / "record an architectural decision" phrasing. Also drops the "another skill needs to maintain the domain model" caveat, since that's the invoking skill's job to state explicitly, not this description's.
- #911 4f28947 Thanks @mattpocock! - Quote the description front matter in to-spec, code-review, setup-matt-pocock-skills, writing-fragments, writing-shape, and wait-what. An unquoted colon-space left over from the em-dash sweep in #905 made each block invalid YAML, so skills.sh skipped all six during discovery and they couldn't be listed or installed via npx skills.
- #917 85f83d3 Thanks @mattpocock! - grilling: update the round template so consecutive questions are separated by a horizontal rule (---) instead of running together.
- #879 d419977 Thanks @mattpocock! - grilling: remove em-dashes from SKILL.md, replacing them with colons and semicolons so the instructions read as plain text.
- #905 e6e9577 Thanks @mattpocock! - Remove every em-dash from the repo's prose (docs, SKILL.md files, ADRs, README.md, scripts, JSON/YAML metadata), hand-rewriting each sentence with a comma, colon, period, parentheses, or conjunction rather than mechanically substituting the character. CLAUDE.md/AGENTS.md now says not to reintroduce them.
- #878 e3e547b Thanks @mattpocock! - Standardize cross-skill invocation on an explicit "call the Skill tool" instruction instead of bare /skill-style prose, across code-review, diagnosing-bugs, grill-with-docs, grill-me, improve-codebase-architecture, tdd, to-spec, to-tickets, triage, and wayfinder.
- A skill that names another skill in prose ("run the /grilling skill") does not reliably cause it to load. This is the documented rough edge behind grill-with-docs's most-reported problem. Naming the tool directly (Call the Skill tool with "grilling") is intended to raise the hit rate. Dropping the leading / also makes the instruction harness-neutral rather than less: it no longer assumes Claude Code's trigger syntax.
- A step needing more than one skill now says so as multiple calls ("Call the Skill tool twice, for grilling and domain-modeling"), not one call carrying two n
v1.3.02026-10-04
Minor Changes
- #1120 2aecca1 Thanks @mattpocock! - Graduate implement-spec into the Engineering bucket, so it ships in the Claude Code plugin, gets a docs page, and is routed by ask-matt as the parallel alternative to per-ticket implement.
implement-spec (user-invoked) implements a whole spec in one run. It reads the tickets as a task graph, runs implementer subagents in their own worktrees across the ready frontier, and lands everything on one integration branch, closing out with code-review. Ahead of graduating:
- The goal is now the integration branch, not a PR. A draft PR opens only when the issue tracker closes work through PRs or you ask for one, and only after the first merge (a branch with no commits ahead of main can't open one). Without a PR, the tickets are resolved the way the tracker closes work.
- It points at the issue tracker like its siblings, telling you to run /setup-matt-pocock-skills when none has been provided, rather than silently defaulting to gh.
- Each implementer confirms its worktree is based on the integration branch, builds its ticket with tdd, and merges the integration tip into its own branch before reporting done, so each merge is a fast-forward.
- #1120 2aecca1 Thanks @mattpocock! - Graduate pr into the Engineering bucket, so it ships in the Claude Code plugin, gets a docs page, and is routed by ask-matt as the PR-body close-out.
pr (model-invoked) is the shape a pull request body should take: a summary as the smallest visual that makes the change clear (pseudocode, a call tree, a file tree, Mermaid, a diff), before/after evidence that it works, and a merge-danger call (one-way or two-way door, plus blast radius). The Summary visuals are adapted from Dex Horthy's show-me, credited in the skill's CREDITS.md.
- #1120 2aecca1 Thanks @mattpocock! - Graduate retro into the Engineering bucket, so it ships in the Claude Code plugin, gets a docs page, and is routed by ask-matt as the last step of the main flow, after code-review.
retro (user-invoked) looks back at a coding session and suggests changes to the agent's environment rather than the code: navigation pointers, automated checks, coding standards, steering files, tool economy, information access. It classifies each coding-standards finding first: a mechanical violation gets a deterministic check (a linter rule, a pre-commit hook, or a CI job), and CODING_STANDARDS.md is kept for genuine judgement calls. A repo with no guardrail at all is a finding in its own right.
- #1120 daa01d8 Thanks @mattpocock! - Remove the resolving-merge-conflicts skill. It's no longer needed, and nothing replaces it: the agent works through an in-progress merge or rebase conflict without a dedicated skill. It leaves the Claude Code plugin, the README and the ask-matt router. Its docs page at https://aihero.dev/skills-resolving-merge-conflicts stays up, marked archived.
- #1120 006a52b Thanks @mattpocock! - Rename the CONTEXT.md/CONTEXT-MAP.md domain-doc convention to GLOSSARY.md/GLOSSARY-MAP.md everywhere the skills read and write it (domain-modeling, grill-with-docs, improve-codebase-architecture, setup-matt-pocock-skills, triage, tdd, diagnosing-bugs, ask-matt, codebase-design, wait-what, pr), plus the docs pages and this repo's own root glossary.
If you have an existing CONTEXT.md (or CONTEXT-MAP.md) from before this change, git mv it to the new name: the skills only look for GLOSSARY.md/GLOSSARY-MAP.md going forward.
Patch Changes
- #848 f02e2ed Thanks @mattpocock! - domain-modeling: trigger on discussing codebase terminology and on writing or editing a GLOSSARY.md or an ADR directly, replacing the narrower "pin down domain terminology or a ubiquitous language" / "record an architectural decision" phrasing. Also drops the "another skill needs to maintain the domain model" caveat, since that's the invoking skill's job to state explicitly, not this description's.
- #911 4f28947 Thanks @mattpocock! - Quote the description front matter in to-spec, code-review, setup-matt-pocock-skills, writing-fragments, writing-shape, and wait-what. An unquoted colon-space left over from the em-dash sweep in #905 made each block invalid YAML, so skills.sh skipped all six during discovery and they couldn't be listed or installed via npx skills.
- #917 85f83d3 Thanks @mattpocock! - grilling: update the round template so consecutive questions are separated by a horizontal rule (---) instead of running together.
- #879 d419977 Thanks @mattpocock! - grilling: remove em-dashes from SKILL.md, replacing them with colons and semicolons so the instructions read as plain text.
- #905 e6e9577 Thanks @mattpocock! - Remove every em-dash from the repo's prose (docs, SKILL.md files, ADRs, README.md, scripts, JSON/YAML metadata), hand-rewriting each sentence with a comma, colon, period, parentheses, or conjunction rather than mechanically substituting the character. CLAUDE.md/AGENTS.md now says not to reintroduce them.
- #878 e3e547b Thanks @mattpocock! - Standardize cross-skill invocation on an explicit "call the Skill tool" instruction instead of bare /skill-style prose, across code-review, diagnosing-bugs, grill-with-docs, grill-me, improve-codebase-architecture, tdd, to-spec, to-tickets, triage, and wayfinder.
- A skill that names another skill in prose ("run the /grilling skill") does not reliably cause it to load. This is the documented rough edge behind grill-with-docs's most-reported problem. Naming the tool directly (Call the Skill tool with "grilling") is intended to raise the hit rate. Dropping the leading / also makes the instruction harness-neutral rather than less: it no longer assumes Claude Code's trigger syntax.
- A step needing more than one skill now says so as multiple calls ("Call the Skill tool twice, for grilling and domain-modeling"), not one call carrying two n
v1.2.32026-08-06
Patch Changes
- #779 efce423 Thanks @mattpocock! - Make diagnosing-bugs redact secrets.
- Add a Redact section to SKILL.md. The skill has the agent show commands, outputs and captured artifacts; the section makes redaction the first move on each — write <REDACTED>, build loops against env vars so the credential stays in the environment, and quote only the signal-carrying lines of a captured artifact.
- The Phase 1 completion criterion said "paste the invocation and its output". It now says show it redacted, and Phase 1 asks the user for a redacted captured artifact.
- Note in scripts/hitl-loop.template.sh that capture prints its value back to the terminal, so it takes observations while signing in stays a step.
- #781 14bfbbd Thanks @mattpocock! - Drop Claude Code's tool and agent-type names from the subagent-dispatch instructions in code-review, codebase-design, and improve-codebase-architecture, so the step is followable on Codex and other harnesses.
- #783 c0fd1e9 Thanks @mattpocock! - wizard: remove the time estimate. The template drops TOTAL_MINUTES and the time-remaining display, stage takes a name only, and progress is counted in stages.
v1.2.22026-08-05
Patch Changes
- #766 4aaccb5 Thanks @mattpocock! - Make writing-for-agents model-invokable in Codex again.
- Drop policy.allowimplicitinvocation: false from agents/openai.yaml. Codex filtered the skill out of the model-visible skills list, so its description could not trigger it — only an explicit $writing-for-agents mention worked.
- Update the stale interface.displayname and interface.shortdescription, which still named the old writing-great-skills skill.
- Move the skill from the User-invoked list to the Model-invoked list in README.md and skills/productivity/README.md.
v1.2.02026-08-05
Minor Changes
- #551 697d4ce Thanks @mattpocock! - Add Codex metadata alongside each skill's Claude Code frontmatter so the set works in both harnesses without generated copies.
- Add an agents/openai.yaml beside every SKILL.md with Codex UI metadata (interface.displayname, interface.shortdescription).
- Mark every user-invoked skill with policy.allowimplicitinvocation: false, the Codex analog of disable-model-invocation: true, so Codex excludes it from implicit invocation while explicit $skill invocation still works.
- Document the dual-harness invocation model in .agents/invocation.md, CLAUDE.md, and the promoted-bucket READMEs.
- Add AGENTS.md as a symlink to CLAUDE.md so Codex reads the same repo instructions.
- #593 0f2bdbd Thanks @mattpocock! - Graduate to-questionnaire out of in-progress/ into the Productivity bucket, so it ships in the plugin. It turns a decision you can't answer alone into a Markdown questionnaire for the one person who can — filled in async, or worked through together in a meeting.
Its defining move is that it grills you about the send, not the subject: a normal grilling session interrogates the topic, which is exactly what you can't answer here, so the interview asks only who the questionnaire is going to and what you need back, then aims every question at the gap between the two.
Now wired as a promoted skill — plugin entry, top-level + Productivity READMEs under User-invoked, a docs page at docs/productivity/to-questionnaire.md, and a Standalone route in ask-matt framing it as the inverse of /grill-me (mine someone else, not yourself).
- #680 b3376f8 Thanks @mattpocock! - Graduate wizard out of in-progress/ into the Engineering bucket, so it ships in the plugin — and make it model-invoked. It generates an interactive bash script that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening each URL, saying what to click, capturing the values, and writing them into .env files and GitHub Actions secrets.
The delightful UX is pre-solved by the bundled template.sh (progress with time-remaining, confirmation gates, cross-platform URL opening including WSL, hidden secret entry, idempotent .env upserts, gh secret/gh variable writes with graceful degradation, closing skip summary). Everything above the STAGES marker is a fixed library that's never hand-edited — the skill's job is only to scope the procedure and author its stages.
Engineering rather than Productivity: it reads .env, docker-compose, framework config and every secrets./vars. reference in .github/workflows/ to scope itself, writes CI secrets, and verifies its output with bash -n and shellcheck.
Because it is model-invoked, the agent can reach for it the moment it hits a step only a human can perform, instead of dumping numbered instructions into the chat and hoping you follow them. Typing /wizard works exactly as before — model-invocation only ever adds the agent's reach. The description is written as the pointer that decides when it fires: what it produces, four trigger branches (provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, a one-off migration or cutover), and an explicit non-trigger — don't invoke it for steps the agent can perform itself. Work an agent can do, an agent should do; the wizard is for the clicks, approvals and dashboard trips you would not hand to one. The stage-list confirmation before a line is written now doubles as the proposal when the agent fires it mid-build.
Now wired as a promoted skill — plugin entry, top-level + Engineering READMEs under Model-invoked, a docs page at docs/engineering/wizard.md, and a Standalone route in ask-matt for the steps only a human can take. Model-invocation also puts it out of the reach of #693, which drops user-invoked skills from the listing on Claude's desktop and web surfaces.
- #763 77d207e Thanks @mattpocock! - Reshape the prototype skill around two ideas: the demo is a single shareable HTML file, and the prototype is a primary source.
The logic branch now produces one self-contained file (plain HTML/CSS/JS, no build, no server) instead of a terminal app — a non-developer can open it by double-click and drive it in their own domain language: a labelled state panel, always-available free-play buttons, and a set of tabbed guided walkthroughs, each a scenario with the ordered buttons to press underneath it. The portable pure-logic module still lifts into the real code; the HTML shell is the throwaway.
Throwaway no longer means deleted. Rather than being removed once it has answered its question, the prototype is captured as runnable evidence on a throwaway branch (prototype/<name>) out of main, with a context pointer to it left on the implementation issue — so the main branch keeps only the validated decision while the exploration stays findable. The answer (verdict + question) is still captured durably in an issue/ADR/commit.
- #536 42a5b70 Thanks @mattpocock! - Ship the skill set as a native Claude Code plugin, listed in Claude Code's official marketplace. You can now subscribe to the promoted skills as a managed, read-only bundle instead of copying editable files:
``bash
claude plugins install mattpocock-skills
`
Or, from inside a session:
`
/plugin install mattpocock-skills
`
There is no marketplace to add first — the official marketplace is configured by default.
.claude-plugin/plugin.json carries the full plugin metadata (version, description, author, license, keywords) and the explicit list of promoted skills. skills.sh remains the universal installer (and the path for Codex and other harnesses today); a native Codex plugin is deferred — see .agents/adr/0002-ship-as-a-claude-code-plugin.md for why.
- #751 355fa74 Thanks @mattpocock! - Add wait-what — a one-word corrective for model verbosity. Type it the moment a message doesn't land, and the agent re-pitches it: a little context, ASD-STE100 Simplified Technical English, and the ubiquitous language from your CONTEXT.md. User-invoked, three lines long.
The mechanism is the name. Concision skills fail by growing — a 400-line skill still leaves the model verbose — so this one is a single precise leading word and nothing else. Names that describe the output (/tldr, /no-fluff) make the model clip words and lose you further; naming the listener's state asks for both halves at once, fewer words and the context you were missing. It also reuses the leading words already in your global CLAUDE.md, so the skill, CLAUDE.md and every CONTEXT.md` reach for the same tokens.
It repairs one message; it doesn't prevent the next one. The cure for
v1.1.02026-07-08
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.
- #464 639df6e Thanks @mattpocock! - Promote and harden code-review. The in-progress review skill is renamed to code-review and moved from in-progress/ into engineering/: it now ships in the plugin, is listed in the top-level and Engineering READMEs (Model-invoked), and has a docs page at docs/engineering/code-review.md. The /implement skill and docs point at /code-review.
It also gains 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) 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.
- #464 639df6e Thanks @mattpocock! - Sharpen grilling on two fronts.
A confirmation gate. 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.
Facts vs. decisions. Grilling now splits facts (look them up — explore the codebase) from decisions (put each one to the human and wait for their answer). The old blanket line — "if a question can be answered by exploring the codebase, explore the codebase instead" — was written for the live-human case, but once another skill runs grilling inside a resolve-the-ticket frame it read as license to answer decisions autonomously too. Separating the two keeps a grilling agent from racing ahead and answering its own questions.
- #463 af6d692 Thanks @mattpocock! - Add two adjacent Steering failure modes to writing-great-skills, both about how language you think of as "off" still steers the agent. Negation — the elephant — is steering by prohibition: naming what not to do drags the forbidden behaviour into context and makes it more available, not less (don't think of an elephant), so the cure is to prompt the positive. Negative Space — the void — is blindness to the steering done by what you leave out: every decision a skill declines is delegated to the agent's priors rather than left neutral, so the cure is to read a draft for its silences and decide each omission deliberately (fill it, or leave it open as a real branch). Kept as two entries, not one — they carry different diagnostics and different cures — each a full GLOSSARY.md entry plus a SKILL.md failure-mode bullet, matching how every other failure mode is carried.
- 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.
- #469 a0329ba Thanks @mattpocock! - Split the to-issues skill into a lean Process and a Reference section, and teach it to handle a wide refactor — a single mechanical change (like renaming a column) whose blast radius fans across the whole codebase, breaking thousands of call sites at once so no vertical slice can land green. The drafting step now points at two co-located reference blocks: the Vertical slice rules for ordinary tracer bullets, and Wide refactors, which slices the change by expand–contract (expand the new form beside the old, migrate call sites in batches sized by blast radius, then contract the old form away) so CI stays green batch to batch — or, when it can't, only at a final integrate-and-verify issue. The issue body template moves into Reference too.
- #464 386d4ff Thanks @mattpocock! - Unify the planning skills. to-prd is renamed to to-spec — "spec" is now the single through-line term (it still opens with "you may know this document as a PRD" for discoverability). to-plan and to-issues are merged into one to-tickets skill, and to-issues is deleted.
to-tickets breaks a plan, spec, or conversation into a set of tickets — tracer-bullet vertical slices, each declaring its blocking edges. That one artifact reads two ways depending on the tracker /setup-matt-pocock-skills configured: a local file (tickets.md) writes the edges as text and you work it top-to-bottom by hand; a real tracker writes them as native blocking links, so any ticket whose blockers are done is on the frontier and several agents can run at once. The edges live in the ticket either way — the medium only decides whether anything acts on them in parallel.
Publishing prefers the tracker's native sub-issues for parent → slice and native blocking edges for Blocked by where the tracker supports them, keeping the ## Parent / ## Blocked by body sections as the
v1.0.12026-06-17
Patch Changes
- d20ee26 Thanks @mattpocock! - Make the teach skill reuse-first. Lessons are now built from reusable components in ./assets/ — stylesheets, quiz widgets, simulators, diagram helpers. Reuse is the default: the agent reads ./assets/ before authoring a lesson, builds from what's there, and extracts anything new and reusable into a component rather than inlining it.
v1.0.02026-06-17
Major Changes
- 47bde84 Thanks @mattpocock! - Add the ask-matt skill — a user-invoked router that points you at the right skill or flow for your situation.
Breaking: ask-matt routes over the other user-invoked skills in this repo, so it expects them to be installed.
- 47bde84 Thanks @mattpocock! - Add the shared design skills and rewire existing skills onto them.
- New codebase-design skill — the deep-module vocabulary (module, interface, depth, seam, adapter) and the principles for putting a lot of behaviour behind a small interface. The language that previously lived in improve-codebase-architecture/LANGUAGE.md now lives here, generalized for reuse across skills.
- New domain-modeling skill — actively build and sharpen a project's domain model, stress-testing terms against the glossary and keeping CONTEXT.md and ADRs current.
- improve-codebase-architecture now draws its architecture vocabulary from /codebase-design and its domain model from /domain-modeling.
- tdd now leans on /codebase-design for interface-design guidance — its inline deep-modules.md / interface-design.md notes were removed in favour of the shared skill.
- grill-with-docs now builds the domain model inline via /domain-modeling.
Breaking: these skills now depend on the new codebase-design / domain-modeling skills, so you must install them too.
- 47bde84 Thanks @mattpocock! - Remove the caveman and zoom-out skills.
- caveman was a duplicate of another skill I was testing and was never meant to be public.
- zoom-out went unused in practice, so it's been removed from the repo.
Breaking: both skills have been removed.
- 47bde84 Thanks @mattpocock! - Rename the diagnose skill to diagnosing-bugs.
Breaking: invoke it as /diagnosing-bugs — the old /diagnose name no longer exists.
- 47bde84 Thanks @mattpocock! - Replace write-a-skill with writing-great-skills.
- Removed write-a-skill.
- Added writing-great-skills (plus its GLOSSARY.md) — a reference for writing and editing skills well: the vocabulary and principles that make a skill predictable, hunting no-ops down to the sentence level.
- Exposed grilling as a model-invoked skill — the reusable interview loop behind grill-me and grill-with-docs.
Breaking: write-a-skill has been removed; use writing-great-skills instead.
Minor Changes
- 47bde84 Thanks @mattpocock! - Add the resolving-merge-conflicts skill — a loop for resolving an in-progress git merge or rebase conflict. Standalone, with no dependencies on other skills.
- 47bde84 Thanks @mattpocock! - Rename the skill taxonomy from Commands / Skills to User-invoked / Model-invoked across the docs, and add docs/invocation.md defining the split: user-invoked skills are reachable only when you type them and exist to orchestrate; model-invoked skills can also be reached automatically when the task fits. A user-invoked skill may invoke model-invoked skills, but never another user-invoked one.
Patch Changes
- 47bde84 Thanks @mattpocock! - Tighten the review skill: fail-fast ref check, single-sourced rules, and no-op cuts.
mattpocock-skills@1.0.02026-06-17
Major Changes
- 47bde84 Thanks @mattpocock! - Add the ask-matt skill — a user-invoked router that points you at the right skill or flow for your situation.
Breaking: ask-matt routes over the other user-invoked skills in this repo, so it expects them to be installed.
- 47bde84 Thanks @mattpocock! - Add the shared design skills and rewire existing skills onto them.
- New codebase-design skill — the deep-module vocabulary (module, interface, depth, seam, adapter) and the principles for putting a lot of behaviour behind a small interface. The language that previously lived in improve-codebase-architecture/LANGUAGE.md now lives here, generalized for reuse across skills.
- New domain-modeling skill — actively build and sharpen a project's domain model, stress-testing terms against the glossary and keeping CONTEXT.md and ADRs current.
- improve-codebase-architecture now draws its architecture vocabulary from /codebase-design and its domain model from /domain-modeling.
- tdd now leans on /codebase-design for interface-design guidance — its inline deep-modules.md / interface-design.md notes were removed in favour of the shared skill.
- grill-with-docs now builds the domain model inline via /domain-modeling.
Breaking: these skills now depend on the new codebase-design / domain-modeling skills, so you must install them too.
- 47bde84 Thanks @mattpocock! - Remove the caveman and zoom-out skills.
- caveman was a duplicate of another skill I was testing and was never meant to be public.
- zoom-out went unused in practice, so it's been removed from the repo.
Breaking: both skills have been removed.
- 47bde84 Thanks @mattpocock! - Rename the diagnose skill to diagnosing-bugs.
Breaking: invoke it as /diagnosing-bugs — the old /diagnose name no longer exists.
- 47bde84 Thanks @mattpocock! - Replace write-a-skill with writing-great-skills.
- Removed write-a-skill.
- Added writing-great-skills (plus its GLOSSARY.md) — a reference for writing and editing skills well: the vocabulary and principles that make a skill predictable, hunting no-ops down to the sentence level.
- Exposed grilling as a model-invoked skill — the reusable interview loop behind grill-me and grill-with-docs.
Breaking: write-a-skill has been removed; use writing-great-skills instead.
Minor Changes
- 47bde84 Thanks @mattpocock! - Add the resolving-merge-conflicts skill — a loop for resolving an in-progress git merge or rebase conflict. Standalone, with no dependencies on other skills.
- 47bde84 Thanks @mattpocock! - Rename the skill taxonomy from Commands / Skills to User-invoked / Model-invoked across the docs, and add docs/invocation.md defining the split: user-invoked skills are reachable only when you type them and exist to orchestrate; model-invoked skills can also be reached automatically when the task fits. A user-invoked skill may invoke model-invoked skills, but never another user-invoked one.
Patch Changes
- 47bde84 Thanks @mattpocock! - Tighten the review skill: fail-fast ref check, single-sourced rules, and no-op cuts.