| /add_cs | Add a new Crop Sales handler to the CRM reporting config (handler groups + team email routing + SharePoint URL) |
| /add_grad_rmt | Mark an RMT handler as graduated — they get the Crop Sales force-release warning instead of the RMT variant |
| /add_no_send | Mark a handler as no-individual-report (resigned, cross-team-only, etc.) in the reporting config |
| /add_rmt | Add a new RMT solo handler to the CRM reporting config (handler groups + email + SharePoint URL) |
| /add_rmt_w_team | Add a new RMT handler with team members to the CRM reporting config (handler groups + email + SharePoint URL) |
| /c-update_crm_doc | Apply drafted documentation updates into the real CRM reporting HTML/page files |
| /inbox | Look up an email in the work inbox by subject keyword and load its content for the current conversation |
| /move_to_EB | Mark a sales handler as moved to Employee Benefits — finds them across handler groups and adds them to the no-report list with a labelled note |
| /no_test | Run an email/report ad-hoc with real configured recipients (no test override) — mirror of /test for production sends |
| /preview | Deploy the current pending code changes into the live checkout and restart the matching app service so the change is visible locally (preview before /push) |
| /push | Update the session continuation notes, commit all changes, push to main — then reflect any portfolio-worthy new work on kendi-ng.com |
| /test | Run the test for the most-recently-edited email/report code, with mandatory safety overrides (drafts only, or a single safe test recipient) |
| /watch-reset | Choose which Claude sessions the auto-resume watcher babysits (resumes after a usage-limit reset). Interactive allowlist. |
| /ask-matt | Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo. |
| /codebase-design | Shared vocabulary for designing deep modules — module interfaces, deepening opportunities, seams, testability |
| /decision-mapping | Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time |
| /design-an-interface | Generate multiple radically different interface designs for a module using parallel sub-agents |
| /diagnosing-bugs | Diagnosis loop for hard bugs and performance regressions |
| /domain-modeling | Build and sharpen a project's domain model — terminology, ubiquitous language, architectural decisions |
| /edit-article | Edit and improve articles by restructuring sections, improving clarity, and tightening prose |
| /git-guardrails-claude-code | Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute |
| /grill-me | A relentless interview to sharpen a plan or design |
| /grill-with-docs | A relentless interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as it goes |
| /grilling | Interview the user relentlessly about a plan or design — stress-test a plan before building |
| /handoff | Compact the current conversation into a handoff document for another agent to pick up |
| /implement | Implement a piece of work based on a PRD or set of issues |
| /improve-codebase-architecture | Scan a codebase for deepening opportunities, present them as a visual HTML report, then work through whichever one you pick |
| /loop-me | Grill through specs for the workflows to build, within the current workspace |
| /migrate-to-shoehorn | Migrate test files from `as` type assertions to a partial-test-data helper library |
| /obsidian-vault | Search, create, and manage notes in an Obsidian vault with wikilinks and index notes |
| /prototype | Build a throwaway prototype to answer a design question before committing to an approach |
| /qa | Interactive QA session where bugs are reported conversationally and filed as GitHub issues, with background codebase exploration for context |
| /request-refactor-plan | Create a detailed refactor plan with tiny commits via interview, then file it as a GitHub issue |
| /resolving-merge-conflicts | Resolve an in-progress git merge/rebase conflict |
| /review | Review changes since a fixed point along two axes — coding standards and spec match — via parallel sub-agents reporting side by side |
| /scaffold-exercises | Create exercise directory structures with sections, problems, solutions, and explainers that pass linting |
| /setup-matt-pocock-skills | Configure a repo for a set of engineering skills — issue tracker, triage label vocabulary, domain doc layout |
| /setup-pre-commit | Set up pre-commit hooks with lint-staged formatting, type checking, and tests in the current repo |
| /tdd | Test-driven development — build features or fix bugs test-first, red-green-refactor |
| /teach | Teach a new skill or concept, within the current workspace |
| /to-issues | Break a plan, spec, or PRD into independently-grabbable issues using tracer-bullet vertical slices |
| /to-prd | Turn the current conversation into a PRD and publish it to the project issue tracker — synthesis, no interview |
| /triage | Move issues and external PRs through a state machine of triage roles — categorise, verify, escalate, write agent-ready briefs |
| /ubiquitous-language | Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms |
| /wizard | Generate an interactive bash wizard that walks a human through a manual procedure, opening URLs, capturing values, confirming each step |
| /writing-beats | Assemble raw material into a journey of beats, grounding each term before a beat leans on it |
| /writing-fragments | Mine raw fragments before any structure exists |
| /writing-great-skills | Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable |
| /writing-shape | Shape raw material into an article, paragraph by paragraph |