Getting started

Introduction

Matt Pocock skills run a spec-to-PR workflow: grill the plan, write a spec, slice tickets, implement test-first, review, then open the PR.

First run

/setup-matt-pocock-skills

Once per repo, before other engineering skills. It explores the repo, confirms answers one section at a time, and writes repo-local markdown. Only the human can invoke it.

See: Setup skill

What setup writes

FileContents
docs/agents/issue-tracker.mdGitHub, GitLab, local markdown, or described workflow
docs/agents/domain.mdSingle- or multi-context doc layout
docs/agents/triage-labels.mdLabel mapping, only with triage installed
CLAUDE.md or AGENTS.md## Agent skills block pointing at those files

See: Setup SKILL.md

Blur to decided

/grill-with-docs add SSO for the admin console

The result is shared understanding you hand to /to-spec; the next sheet covers how the interview runs.

See: grill-with-docs

Decided to tickets

/to-spec add SSO for the admin console
/to-tickets #42

/to-spec synthesises the conversation without a new interview; /to-tickets slices the spec into demoable work with blocking edges.

See: to-spec

Tickets to PR

/implement #43
/code-review main
/pr

One ticket per fresh context. /implement drives red-green tests at the agreed seams, calls review and commits; /pr shapes the body.

See: pr

The pipeline

Flow

/grill-with-docs ─▶ /to-spec ─▶ /to-tickets ─▶ /implement
        │                                              │
        ├─ GLOSSARY.md, ADRs                          ├─▶ /code-review
        └─ /wayfinder when multi-session             └─▶ /pr ─▶ /retro
/triage ─▶ ready-for-agent ─▶ /implement

See: Flow map

Gates

CommandEnd state
/grill-with-docsfrontier empty, user confirms shared understanding
/to-specseam check confirmed, spec published ready-for-agent
/to-ticketsnumbered breakdown approved, demoable slices with blocking edges
/implementtypecheck, single tests, full suite once, review, commit
/code-reviewresolvable fixed point, non-empty diff, Standards and Spec reports
/prbody has Summary, before/after Evidence, door and blast radius

See: Flow map

Which command

Find the skill

CommandSituation
/ask-mattUnsure which skill fits
/grill-meIdea is fuzzy, no repo
/grill-with-docsFuzzy, in a repo
/wayfinderFog spans sessions
/to-specDecided, need a durable spec

Build the work

CommandSituation
/to-ticketsSpec ready to slice
/implementDecided, ready to code
/implement-specWhole spec, many tickets

See: Router

Around the flow

CommandRole
/triageMoves incoming issues through state roles to ready-for-agent
/handoffWrites a portable summary into the OS temp dir
/retroSuggests changes to the agent's environment after a session

See: Triage

Invocation

  • Human only /grill-me, /grill-with-docs, /to-spec, /implement, /triage, /setup-matt-pocock-skills
  • Model or human, via Skill tool grilling, tdd, code-review, pr
  • Never A Skill tool call to a user-invoked skill

See: Invocation rules

Planning

Spec

  • Problem Statement The problem from the user's perspective
  • Solution The solution from the user's perspective
  • User Stories Numbered "As an actor, I want..." stories
  • Implementation Decisions Modules, interfaces, constraints, no file paths
  • Testing Decisions Good-test rule, modules, prior art
  • Out of Scope Refused work
  • Further Notes Anything left over

See: to-spec

Tickets

  • Tracer bullet Narrow path through schema, API, UI and tests
  • Demoable Verifiable on its own
  • Single context Sized for one fresh context window
  • Blocking edges Prerequisites; work the frontier first
  • Wide refactor Expand, migrate in batches, then contract

See: to-tickets

Domain docs

Glossary

**Invoice**:
A request for payment sent to a customer after delivery.
_Avoid_: Bill, payment request

ADRs

# Write model

Orders go to Postgres; the read model is projected into Redis.

Terms go into GLOSSARY.md inline. An ADR needs all three gates: hard to reverse, surprising, a real trade-off.

See: domain-modeling

Tracker

TrackerTicket store
GitHubIssues via gh
GitLabIssues via glab
Local markdownFiles under .scratch/<feature>/issues/NN-slug.md
OtherFreeform workflow described in prose

See: Local tracker template

Building

Implement

CommandUse
/implement #43One ticket, one commit on the current branch
/implement-specWhole spec on an integration branch

See: implement

TDD loop

red   -> failing test at an agreed seam
green -> minimum code to pass

Pitfalls

  • One slice at a time Repeat red-green; refactoring belongs in review
  • Implementation-coupled Breaks on refactor, not behaviour
  • Tautological Assertion recomputes the expected value

See: tdd

Review and PR

## Summary
<diagram, diff-sketch, or tree>
## Evidence
**Before:** <screenshot or failing run>
**After:** <screenshot or passing run>
## Merge Danger
**Door:** two-way
**Blast Radius:** docs only

See: code-review

0 Comments for this cheatsheet. Write yours!