codex

Matt Pocock Engineering

An unofficial, conservative Matt Pocock engineering workflow bundle for Codex.

2 on GitHubby Yewang Tsaiv2.2.2+codex.20260825111023MITupdated 2 months agoProductivity

Plugin matt-engineering in tsai09495/matt-pocock-engineering. Commands read from the repo's manifest — 1 month ago.

This plugin runs code on your machine — it starts local MCP servers. The exact commands are listed below; read them before installing.

What it installs

Skills (19)

  • ask-matt

    Recommend the smallest Matt Pocock Engineering flow that fits the current task. Use when the user asks which workflow to use, where to start, or whether a heavier engineering process is warranted.

  • code-review

    Review working-tree, branch, commit, or PR changes on separate Standards and Spec axes. Use for code review, uncommitted-change inspection, or checking a diff against source requirements.

  • codebase-design

    Design deep modules with small interfaces and clean seams. Use when shaping module boundaries, improving testability, placing an interface, or applying Matt's shared codebase-design vocabulary.

  • diagnosing-bugs

    Diagnosis loop for unclear, hard, flaky, or performance-sensitive bugs. Use when the user asks to diagnose/debug, when a repro or feedback loop is needed, or when a reported failure's cause/fix is not already obvious.

  • domain-modeling

    Build and sharpen a project's domain model and proposed glossary or ADR updates. Use when resolving domain terminology, ubiquitous language, or a durable domain decision.

  • grill-with-docs

    Challenge and sharpen a plan against repository evidence, domain language, and ADRs. Use for a dependency-safe decision interview or when assumptions must be resolved before a spec or implementation.

  • handoff

    Carry essential working context to another task, directory or worktree, harness, collaborator, or mid-phase side fork in a portable Markdown handoff.

  • implement

    Implement an already-defined spec, ticket, issue, or bounded behavior and verify the diff. Use for real code changes from established requirements, not open-ended planning or unknown-cause bugs.

  • improve-codebase-architecture

    Find high-leverage deepening opportunities in a codebase. Use for architecture health, refactoring candidates, tightly coupled modules, testability, or AI navigability.

  • prototype

    Build an explicitly throwaway prototype after the user asks for one or agrees it is useful: one self-contained HTML file for logic/state questions, or several UI variations toggleable from one route.

  • research

    Research a bounded engineering question from primary sources. Use for official documentation, source code, specifications, or APIs, especially when findings need a cited Markdown artifact.

  • resolving-merge-conflicts

    Use when you need to resolve an in-progress git merge/rebase conflict.

  • setup-matt-pocock-skills

    Configure repository-wide Matt Engineering tracker, triage, domain-doc, and Wayfinding conventions. Use only when the user explicitly selects Setup to initialize Matt workflows.

  • tdd

    Develop concrete behavior test-first through one RED and GREEN vertical slice at a time. Use for TDD, test-first development, red-green-refactor, or behavior-led implementation.

  • to-spec

    Turn established context into a durable spec draft. Use to document an already-discussed feature, synthesize requirements, or publish a reviewed spec. Always call the artifact a spec, even when the user says PRD.

  • to-tickets

    Break a plan, spec, or established conversation into implementable tracer-bullet tickets with explicit blocking edges. Use when the user asks to split work into tickets, issues, or independently executable slices.

  • triage

    Triage incoming issues or external PRs through configured triage roles. Use when the user asks to list, evaluate, label, move, close, or write agent-ready briefs for issue-tracker items.

  • wayfinder

    Map a huge, foggy engineering effort into durable decision tickets. Use only when the user explicitly selects Wayfinder for a multi-session destination with dependent unknowns.

  • wizard

    Generate a reviewed interactive Bash wizard for manual steps only a human can perform. Use for third-party dashboard setup, credential capture, CI secrets, or a human-driven cutover—not ordinary agent-executable work.

MCP servers (1)

  • mattEngineeringCompatibilityBridge

    runs: node ./mcp/server.cjs --stdio

View source on GitHub

Similar plugins

caveman

claude

Talk like caveman. Cut filler. Keep technical details explicit.

22 skills · 1 command · 3 agents · hooks

JuliusBrussee/caveman 119,462

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

Taste Skill

claudecodex

tasteskill 2.5.1: professional company websites at the figma.com and x.ai level, with one section per screen, real photographs, real product UI, effects kept for tech and gaming pages, and a real-browser checker and finish gate.

1 skill

Leonxlnx/taste-skill 114,391

career-ops

claudecodex

Open-source AI job search that runs locally in your AI coding CLI: scan job portals, evaluate listings into a structured A-H report with a 1-5 score, tailor your CV, track applications

5 skills · hooks

career-ops-hq/career-ops 82,253

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

pake

claudecodex

Package any website or local web build into a lightweight desktop app with Pake CLI.

1 skill

tw93/Pake 63,463

Maintain Matt Pocock Engineering?

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.

claude & codex pluginslisted