Agent bundles / matt-pocock
Matt Pocock engineering workflow skills.
Understanding-oriented
Why the bundle is built this way.
matt-pocock holds an engineering workflow: domain modelling, tickets, triage, test-driven development, code review and implementation. Local Markdown tickets are the source of truth. ALIGNMENT-ROOT.md describes how these skills find tickets, initiatives, workflows and evidence from one active alignment root.
Learning-oriented
Use the matt-pocock bundle for the first time.
/matt-pocock:grilling in Claude Code, or /skill:grilling in OMP.Task-oriented
Steps for one task each.
| Harness | Steps |
|---|---|
| Claude Code | Raise version in .claude-plugin/plugin.json and in the marketplace.json entry, then run: claude plugin update matt-pocock@zenobius-agent-bundles. Start a new session. |
| OMP | Start a new session. The symlink shows the change at once. |
| Pi | Start a new session. The symlink shows the change at once. |
| Zot | Start a new session. The symlink shows the change at once. |
Information-oriented
Read from the bundle files at build time.
| Part | Claude Code | OMP | Pi | Zot | Codex |
|---|---|---|---|---|---|
| Skillsskills/**/SKILL.md. Instructions that the agent or the user invokes. | supported | supported | supported | supported | not supported |
| Harness | Install | Reads |
|---|---|---|
| Claude Code | mise run claude.bootstrap (runs claude plugin install matt-pocock@zenobius-agent-bundles) | .claude-plugin/plugin.json, skills/, agents/*.md, hooks/hooks.json |
| OMP | mise symlinks ~/.omp/agent/bundles/matt-pocock to the bundle | package.json (pi key), skills/, agents/*.md, extensions/ |
| Pi | mise symlinks ~/.pi/agent/bundles/matt-pocock to the bundle | package.json (pi key), skills/, agents/*.md, extensions/ |
| Zot | mise symlinks ~/.local/state/zot/extensions/matt-pocock to the bundle | extension.json, skills/ |
28 skills
| Skill | Invoked by | Scripts | Description |
|---|---|---|---|
| ask-matt | user only | — | Ask which skill or flow fits your situation. A router over the skills in this repo. |
| code-review | user and agent | — | Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X". |
| codebase-design | user and agent | — | Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary. |
| diagnosing-bugs | user and agent | yes | Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow. |
| domain-modeling | user and agent | — | Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model. |
| feature-request | user and agent | — | Investigate and submit a repository feature request, when a user has a repository and feature idea, resulting in a feasibility report and a repository-compliant request only when the idea remains viable |
| grill-me | user only | — | A relentless interview to sharpen a plan or design. |
| grill-with-docs | user only | — | A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go. |
| grilling | user and agent | — | Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases. |
| handoff | user only | — | Compact the current conversation into a handoff document for another agent to pick up. |
| implement | user and agent | — | Implement a piece of work based on a spec or set of tickets. |
| improve-codebase-architecture | user and agent | — | Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick. |
| prototype | user and agent | — | Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like. |
| reading-and-writing-tickets | user and agent | yes | Set up trackers; read, list, create, update, validate, and migrate initiatives (specs) and tickets; claim, review, complete, and map executable tickets. Owns versioned record schemas, publication, membership, and results. |
| research | user and agent | — | Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent. |
| resolving-merge-conflicts | user and agent | — | Use when you need to resolve an in-progress git merge/rebase conflict. |
| setup-matt-pocock-skills | user and agent | — | Guide the user through the Matt Pocock setup questionnaire, obtain plan approval, and delegate configuration and verification to reading-and-writing-tickets setup. |
| tdd | user and agent | — | Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests. |
| teach | user only | — | Teach the user a new skill or concept, within this workspace. |
| to-questionnaire | user and agent | — | Turn a decision you can't fully answer into a questionnaire for someone else to fill in. |
| to-spec | user only | — | Synthesize the current conversation into a specification and publish it as an initiative through the configured tracker. |
| to-tickets | user and agent | — | Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker). |
| triage | user and agent | — | Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs. |
| wait-what | user only | — | Stop. That last message did not land: re-pitch it. |
| wayfinder | user and agent | — | Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear. |
| wizard | user and agent | — | Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself. |
| writing-for-agents | user and agent | — | Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md. |
| writing-great-skills | user and agent | — | Compatibility alias for writing-for-agents. |