matt-loop
v4.0.0Matt Pocock design with the user via matt-design; confirmed-spec autonomous tickets, implementation, verification and independent review via matt-auto. Includes PR babysitting and conflict resolution. Requires weed-harness 6.0+.
By weedmoLicense: MIT1 GitHub starsUpdated 3 days ago
Directory evidence
- Runtimes
- Codex
- Parsed components
- 19 skill or MCP entries
- Source updated
- Sep 21, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install matt-loop for Codex
codex plugin marketplace add weedmo/skills
codex plugin marketplace upgrade weed-plugins
codex plugin add matt-loop@weed-pluginsPaste and run these commands in a terminal with Codex. They add and refresh the weed-plugins catalog, then install this plugin.
Compatibility: the page URL and API slug “matt-loop-3” remain stable.
- Codex:
matt-loop-3@agent-plugin-marketplace→matt-loop@weed-plugins
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/weedmo/skillsClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/matt-loop-codex/.
Plugin files
├── .codex-plugin/plugin.json├── skills/code-review/SKILL.md├── skills/codebase-design/SKILL.md├── skills/diagnosing-bugs/SKILL.md├── skills/domain-modeling/SKILL.md├── skills/grill-me/SKILL.md├── skills/grill-with-docs/SKILL.md├── skills/grilling/SKILL.md├── skills/handoff/SKILL.md├── skills/implement/SKILL.md├── skills/improve-codebase-architecture/SKILL.md├── skills/matt-auto/SKILL.md├── skills/matt-design/SKILL.md├── skills/pr-babysit/SKILL.md├── skills/prototype/SKILL.md├── skills/resolving-merge-conflicts/SKILL.md├── skills/setup-matt-pocock-skills/SKILL.md├── skills/tdd/SKILL.md├── skills/to-spec/SKILL.md└── skills/to-tickets/SKILL.md
Included Skills19
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/spec 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".
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.
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a CONTEXT.md, or recording or editing an ADR.
A relentless interview to sharpen a plan or design.
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
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.
Compact the current conversation into a handoff document for another agent to pick up.
Implement a piece of work based on a spec or set of tickets.
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Execute a confirmed local spec: create tickets, implement, verify, and independently review with bounded fix cycles. Use --spec PATH; design and user iteration belong to matt-design, visualization to design-map. Autonomous by default; --confirm requests a ticket/execution-plan gate. --dev / --main / --pr BASE enable PR shipping; --parallel N caps concurrency. --on ENV selects Orca placement; --free uses free-only OpenCode routing.
Collaboratively design a feature or change using Matt Pocock's grilling, domain-modeling, codebase-design, prototype, and to-spec skills. Iterate decisions with the user and write a local confirmed spec for matt-auto. Use for design before implementation; design-map renders the current design as an artifact.
Use when the user wants you to babysit, watch, monitor, or shepherd one open GitHub PR until it is merge-ready by handling its checks, review feedback, and PR-caused failures. Does not merge unless explicitly requested. On Codex, OpenCode, and Claude Code, direct invocation automatically routes work by complexity (model and reasoning effort).
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.
Resolve an in-progress git merge/rebase conflict. Codex and OpenCode start with latency-sensitive routing and escalate only on a concrete reasoning limit.
Configure this repo for the engineering skills: set up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.
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).
Plugin manifests1
{
"name": "matt-loop",
"version": "4.0.0",
"description": "Matt Pocock design with the user via matt-design; confirmed-spec autonomous tickets, implementation, verification and independent review via matt-auto. Includes PR babysitting and conflict resolution. Requires weed-harness 6.0+.",
"author": {
"name": "weedmo",
"url": "https://github.com/weedmo"
},
"homepage": "https://github.com/weedmo/skills",
"repository": "https://github.com/weedmo/skills",
"license": "MIT",
"keywords": [
"codex",
"skills",
"workflow",
"productivity"
],
"skills": "./skills/",
"interface": {
"displayName": "matt-loop",
"shortDescription": "Collaborative Matt design and autonomous confirmed-spec execution",
"longDescription": "Use matt-design to iterate design decisions with the user and produce a confirmed local spec. Invoke matt-auto --spec separately to create tickets, implement, verify and independently review. design-map in weed-harness visualizes the current design. Optional flags enable PR shipping.",
"developerName": "weedmo",
"category": "Coding",
"capabilities": [
"Interactive",
"Read",
"Write"
],
"defaultPrompt": [
"Use $matt-design to design this change with me.",
"Use $matt-auto --spec docs/design/feature.md to implement and review the confirmed design."
],
"brandColor": "#2563EB",
"screenshots": []
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[matt-loop on Agent Plugins Marketplace](https://pluginsmp.com/plugins/matt-loop-3)