mattpocock-skills
claudeMatt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Generic Shape Up workflow: shape → bet → scope → build → ship, with an autonomous agent fleet (shaper, product-strategist, engineer, debugger, reviewer, researcher, closer) and inline methodology skills. Drive each step by hand or orchestrate the whole loop with /cycle.
Plugin shapeup from marketplace rafoflow in rafae2k/rafoflow. Commands read from the repo's manifest — 24 days ago.
betEvaluate a shaped pitch: bet on it, kill it, or send it back for reshaping. Use after /shape to decide if something is worth building.
cutScope-hammer: when you're over appetite or overwhelmed, this skill helps decide what to cut. Use when things are taking longer than expected.
cycleRun a full Shape Up cycle end-to-end — research → shape → bet → scope → build → review → ship — orchestrated in one flow with persistent artifacts and two human checkpoints. Use when you want the whole workflow driven for you instead of invoking each skill by hand.
debugSystematic debugging using the scientific method. Use when something is broken and you need to find the root cause, not just make symptoms disappear.
engineerSenior software engineer coding assistant. Embeds design principles, debugging mental models, and code quality standards. Use when you want disciplined, principled code — not just code that works.
exploreResearch-only step, standalone: explore an idea, run a spike, check feasibility, understand a problem space. No cycle, no task, read-only on product code. Ends in an explicit exit — cycle, task, backlog, or dies here.
flow-routerDecision tree for the Shape Up workflow — picks which agent or skill to use for a given situation (have an idea, should we build it, build it, something's broken, ready to ship). Use when unsure which part of the shapeup workflow applies, or to see the full cycle from pitch to ship.
market-researchDeep research on any healthtech topic using Exa search. Finds scientific papers, expert articles, market reports, and industry analysis. Use when you need evidence-based data on healthcare markets, technologies, regulations, or business models.
reviewCode review focused on simplicity, blast radius, and less software. Use after building to check quality before shipping.
scopeBreak a shaped pitch into buildable scopes — independent slices of work that each deliver value. Use after betting on a pitch, before starting to build.
setupMake a repo agent-ready: find every environment variable the code really uses, name and comment them all in a .env.example, wire the real env file safely, and write the agent rules plus the real-data commands those variables unlock. Use when env is missing or undocumented, when onboarding a repo, or
shapeTake a raw idea or feature request and shape it into a buildable pitch with fixed appetite. Use when you have a new idea, vague requirement, or feature request that needs scoping.
shipPre-ship checklist and launch copy. Fights the 'one more thing' instinct. Use when you're done building but haven't shipped yet.
taskSmall, already-understood change (new column, ordering, label, filter, localized fix). Use when scope fits one sentence and a few files, with no direction decision. Short plan in chat, code + test, gate, ship. No research/pitch/spec, no cycle folder.
closerGets things shipped. Pre-ship checklist, launch copy, store/release metadata, release notes. Fights 'one more thing' instinct. Use when you're done building and need to actually release.
debuggerAutonomous debugger. Reproduces bugs, forms hypotheses, tests them systematically, finds root causes. Use when something is broken and you need the actual cause, not a band-aid.
engineerAutonomous senior software engineer. Takes a scoped task and builds it end-to-end: reads existing code, implements the change, runs build/tests, fixes issues. Use for implementation work that needs discipline and quality.
product-strategist37signals-inspired product strategist. Makes bet-or-kill decisions, challenges scope creep, enforces 'build half a product not a half-assed product.' Use when deciding WHAT to build, prioritizing features, or questioning whether something belongs in the product.
researcherAutonomous deep researcher using Exa search. Investigates any topic: technical approaches, market data, scientific papers, competitor analysis, design patterns. Produces evidence-based research briefs with citations. Use before shaping or when you need data to make a decision.
reviewerAutonomous code reviewer. Reads recent changes, analyzes quality, and produces actionable review focused on simplicity and blast radius. Read-only — never modifies code. Use after building to check quality before shipping.
shaperTakes a raw idea, problem, or feature request and autonomously shapes it into a buildable pitch with fixed appetite. Researches the problem space, identifies rabbit holes, and produces a complete Shape Up pitch. Use when you have a vague idea that needs scoping before building.
spec-reviewerIndependent spec reviewer. Receives only the spec (plus repo and read access to production) and a role — architecture, facts, or production — and attacks it from that angle. Read-only. Use on class A/B specs before the build starts.
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
15 skills · hooks
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
Automates browser interactions for web testing, form filling, screenshots, and data extraction
12 skills
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.