← all plugins

1. ▌
   qa · fradser

   Interactive QA session where user reports bugs or issues conversationally, and the agent files GitHub issues. Explores the codebase in the background for context and domain language. Use when user wants to report bugs, do QA, file issues conversationally, or mentions "QA session".
   580
   repo stars
2. ▌
   bdd · fradser bundle

   Behavior-driven development: Discovery → Formulation → Automation. Use when the user wants to build features or fix bugs via Gherkin scenarios and the BDD lifecycle, or mentions BDD/Gherkin/Executable Specifications. Delegates test implementation to /mattpocock:tdd.
   580
   repo stars
3. ▌
   tdd · fradser bundle

   BDD-driven test implementation: red-green loop mechanics, seams, mocking, and test quality under BDD Automation. Use when the user wants to write or improve tests during BDD implementation, needs guidance on test structure, or asks about test seams, mocking, or anti-patterns.
   580
   repo stars
4. ▌
   triage · fradser bundle

   Moves issues and external PRs through a state machine of triage roles — categorise, verify, grill, and write agent-ready briefs. Use when the user says "triage this issue" or wants agent-ready issue briefs.
   580
   repo stars
5. ▌
   wizard · fradser bundle

   Generates an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, running a one-off migration or cutover, or the user says "build a wizard" or wants a scripted step-by-step setup. Don't invoke this for steps the agent can perform itself.
   580
   repo stars
6. ▌
   teach · fradser bundle

   Teaches the user a new skill or concept within the workspace. Use when the user says "teach me X", wants to learn a topic over sessions, or needs a structured learning plan.
   580
   repo stars
7. ▌
   to-spec · fradser bundle

   Turns the current conversation into a spec and publishes it to the project issue tracker, with no interview. Use when the user says "write a spec", "create a PRD", or wants the discussion captured as a spec.
   580
   repo stars
8. ▌
   loop-me · fradser bundle

   Runs a stateful grilling session that produces workflow specs for workflows the user wants to build. Use when the user says "loop me" or wants workflow specs drawn out of them.
   580
   repo stars
9. ▌
   ask-matt · fradser bundle

   Recommends the skill or flow that fits the user's situation. A router over the skills in this repo. Use when the user asks which skill to use, is unsure what fits, or needs a pointer to the right workflow.
   580
   repo stars
10. ▌
    handoff · fradser bundle

    Compacts the current conversation into a handoff document for another agent to pick up. Use when the user says "hand this off" or wants the work continued by a fresh session.
    580
    repo stars
11. ▌
    implement · fradser bundle

    Implements a piece of work from a spec or ticket set. Use when the user says "implement this spec", "work the tickets", or wants code written from an existing plan.
    580
    repo stars
12. ▌
    prototype · fradser bundle

    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.
    580
    repo stars
13. ▌
    wayfinder · fradser bundle

    Plans a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on the issue tracker, resolved one at a time. Use when the user has a large ambiguous goal and wants the route charted.
    580
    repo stars
14. ▌
    setup-pre-commit · fradser bundle

    Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
    580
    repo stars
15. ▌
    edit-article · fradser

    Edit and improve articles by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, or improve an article draft.
    580
    repo stars
16. ▌
    grill-me · fradser bundle

    Runs a relentless interview that sharpens a plan or design. Use when the user wants to be grilled on an idea, pressure-test a plan, or refine a design through questioning.
    580
    repo stars
17. ▌
    grilling · fradser bundle

    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.
    580
    repo stars
18. ▌
    to-tickets · fradser bundle

    Breaks a plan, spec, or conversation into tracer-bullet tickets that declare their blocking edges, published to the configured tracker. Use when the user says "break this into tickets" or wants a plan decomposed into vertical slices.
    580
    repo stars
19. ▌
    wait-what · fradser bundle

    Stop. That last message did not land — re-pitch it. Use when the user says "wait what", "I don't follow", "explain that again", or similar confusion signals.
    580
    repo stars
20. ▌
    code-review · fradser bundle

    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/PRD 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".
    580
    repo stars
21. ▌
    scaffold-exercises · fradser bundle

    Create exercise directory structures with sections, problems, solutions, and explainers that pass linting. Use when user wants to scaffold exercises, create exercise stubs, or set up a new course section.
    580
    repo stars
22. ▌
    obsidian-vault · fradser

    Search, create, and manage notes in the Obsidian vault with wikilinks and index notes. Use when user wants to find, create, or organize notes in Obsidian.
    580
    repo stars
23. ▌
    migrate-to-shoehorn · fradser bundle

    Migrate test files from `as` type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace `as` in tests, or needs partial test data.
    580
    repo stars
24. ▌
    writing-beats · fradser bundle

    Exploit-phase writing — assembles raw material into a journey of beats, grounding each term before a beat leans on it. Use when the user has raw material and wants it turned into an article.
    580
    repo stars
25. ▌
    writing-shape · fradser bundle

    Exploit-phase writing — shapes raw material into an article paragraph by paragraph. Use when the user has a raw-material pile and wants the final article written.
    580
    repo stars
26. ▌
    batch-grill-me · fradser

    Runs a relentless interview that asks every frontier question at once, round by round. Use when the user wants to be grilled on a design or map a design tree.
    580
    repo stars
27. ▌
    claude-handoff · fradser bundle

    Hands the current conversation to a fresh background agent that picks up the work immediately. Use when the user wants the work continued by a background agent.
    580
    repo stars
28. ▌
    codebase-design · fradser bundle

    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.
    580
    repo stars
29. ▌
    diagnosing-bugs · fradser bundle

    Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
    580
    repo stars
30. ▌
    domain-modeling · fradser bundle

    Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
    580
    repo stars
31. ▌
    grill-with-docs · fradser bundle

    Runs a relentless interview that sharpens a plan or design and creates docs (ADRs and glossary) along the way. Use when the user wants to stress-test a plan or design, or produce decision records.
    580
    repo stars
32. ▌
    writing-fragments · fradser bundle

    Explore-phase writing — mines raw fragments without committing to structure. Use when the user wants to brainstorm material or gather fragments for a later article.
    580
    repo stars
33. ▌
    to-questionnaire · fradser bundle

    Turns a decision the user can't fully answer into a questionnaire for someone else to fill in. Use when the user says "turn this into a questionnaire" or needs knowledge pulled out of an expert.
    580
    repo stars
34. ▌
    design-an-interface · fradser

    Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
    580
    repo stars
35. ▌
    ubiquitous-language · fradser

    Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
    580
    repo stars
36. ▌
    git-guardrails-claude-code · fradser bundle

    Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
    580
    repo stars
37. ▌
    writing-for-agents · fradser bundle

    Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
    580
    repo stars
38. ▌
    request-refactor-plan · fradser

    Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
    580
    repo stars
39. ▌
    setup-ts-deep-modules · fradser bundle

    Wires dependency-cruiser into a TypeScript repo so each package is a deep module — implementation hidden in subfolders, reachable only through entry-point files. Use when the user wants deep-module enforcement or dependency-cruiser setup.
    580
    repo stars
40. ▌
    writing-great-skills · fradser bundle

    Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable. Use when the user asks "how should I write a skill" or wants skill-writing best practices.
    580
    repo stars
41. ▌
    setup-matt-pocock-skills · fradser bundle

    Configures a repo for the engineering skills — issue tracker, triage label vocabulary, and domain doc layout. Use once before first use of the other engineering skills, when the user says "set up the skills" or "initialize repo config".
    580
    repo stars
42. ▌
    resolving-merge-conflicts · fradser bundle

    Use when you need to resolve an in-progress git merge/rebase conflict.
    580
    repo stars
43. ▌
    improve-codebase-architecture · fradser bundle

    Scans a codebase for deepening opportunities, presents them as a visual HTML report, then grills through the chosen one. Use when the user wants to improve codebase architecture or find refactoring opportunities.
    580
    repo stars