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.
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.
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.
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.
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.
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.
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.
Find high-leverage deepening opportunities in a codebase. Use for architecture health, refactoring candidates, tightly coupled modules, testability, or AI navigability.
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 a bounded engineering question from primary sources. Use for official documentation, source code, specifications, or APIs, especially when findings need a cited Markdown artifact.
Configure repository-wide Matt Engineering tracker, triage, domain-doc, and Wayfinding conventions. Use only when the user explicitly selects Setup to initialize Matt workflows.
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.
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.
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 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.
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.
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.
★not rated 2 10d agoA43 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: