skills

Plugin skills from marketplace mvdmio in michielvandermeer/skills. Commands read from the repo's manifest — 3 days ago.

Skills (27)

• verify

  Drive this checkout's skills the way a user does — load the working tree as the plugin in a headless Claude Code session inside a scratch repo, type the slash commands and answers, and capture what the skill did. Use to prove a skill or agent edit behaves before it is committed or pushed, or when as

• brainstorm

  Explore a vague problem as very different Directions, side by side, and file the ones you keep as Issues.

• code-review

  Review changes since a commit, branch, or tag against the coding standards and the Spec. Use when the user wants a branch, a PR, or work in progress reviewed.

• doctor

  Moves documents into this project's canonical layout, closes local Issues the code already implements, brings every ADR to state the decision in force, trims oversized Coding standards to one short line per rule, and cleans repeats, dead paths, and contradictions out of Steering files.

• domain-modeling

  Build and sharpen a project's domain model, its glossary and ADRs. A Library skill other skills read by path.

• explain

  Explain anything as a written walkthrough, a diagram in the chat, an HTML page, or a narrated video, picking the format that fits.

• grill-with-docs

  A relentless round-by-round interview to sharpen a plan or design, which also creates docs (ADRs and glossary) as we go.

• grilling

  Grill the user relentlessly about a plan or design, round by round. A Library skill other skills read by path.

• hillclimb

  Hillclimb one measured number — test-suite time, build time, memory, bundle size — keeping only the changes that measurably help. Use when the user wants something made faster, smaller, or cheaper, as far as it will go or past a target.

• hunt-codebase-improvements

  Hunt your codebase for improvements along eight axes, such as state bugs, cruft, slow pages, and wasted CI time, then triage what the hunt finds into Issues.

• implement

  Implement a spec by slicing it into steps, then a loop of implement, review, and verify, each in its own sub-agent. Use only when the user or a /goal names /implement.

• learn-habits

  Rebuild a person's Grilling profile from the Habits in their past grilling sessions.

• pr

  Pull request descriptions. Use when writing the description of a pull request or merge request.

• prototype

  Build a throwaway prototype to answer a design question, then turn the answer into a Spec. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

• research

  Investigate a question against high-trust primary sources and capture the findings as a Markdown file in the repo. Use when the user wants a topic researched, docs or API facts gathered, or reading legwork delegated to a background agent.

• resolving-merge-conflicts

  Resolve git merge or rebase conflicts. Use when the user asks to merge or rebase and resolve the conflicts, or when a merge or rebase stops on a conflict.

• retro

  Read a window of past sessions, apply high-priority changes this repository owns for lessons that repeat, file the structural ones as Issues, and summarise the rest.

• setup

  Set up or update the repo's Tracker ref, where its Issues live; its Verify skill, which drives the app the way a user does; or its Models ref, the model and effort each plugin agent runs at.

• simulate-first-users

  Send five simulated first-time users through your app in real browsers, then triage what tripped them up into Issues with screenshots.

• technical-writing

  The house standard for every sentence a person reads. A Library skill other skills read by path.

• to-spec

  Turn the current conversation into a Spec and write it onto its Issue in the repo's Tracker — no interview, just synthesis of what you've already discussed.

• triage

  Sort incoming reports into Specs and parked Issues — one Issue per distinct problem.

• validate-spec

  Validate an Issue, a Spec, a plan, or the current conversation against this repo's own template rules and the current codebase — fix stale references and contradictions in place, flag real decisions as open questions.

• wayfinder

  Plan a change too big for one agent session as a shared map of decision tickets in the repo's Tracker, resolved one at a time until the way is clear and its Specs can be written.

• what-did-i-get-done

  Summarise what you got done over a period, from your commits, pull requests, and Issues in this repo.

• why

  Trace why code is the way it is, with every claim cited. Use for "why does X work this way", why a choice was made, a regression's origin, or before changing code that looks deliberate.

• writing-for-agents

  Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.

Subagents (9)

• climber

  Writes one Attempt of a /hillclimb run — a single idea, left uncommitted for the driving session to measure. Dispatched explicitly by /hillclimb — it works to a contract decided before it starts, so it is not a general coding agent.

• cold-reader

  Reads the Spec draft /to-spec has just written with nothing else and explains it back, naming each place it had to guess. Dispatched explicitly by /to-spec — it works to a contract decided before it starts, so it is not a general coding agent.

• explorer

  Walks a codebase read-only and reports what it finds, without changing anything.

• implementer

  Implements one Step of a Spec, or fixes what the last review or verify found, during an /implement run. Dispatched explicitly by /implement — it works to a contract decided before it starts, so it is not a general coding agent.

• planner

  Slices a Spec into Step files at the start of an /implement run, commits them, and returns only the compact index. Dispatched explicitly by /implement — it works to a contract decided before it starts, so it is not a general coding agent.

• researcher

  Investigates one question against primary sources and writes the findings to a Markdown file. Dispatched by /research to run in the background while the main session keeps working.

• reviewer

  Reviews the changes since a fixed point along one axis — Standards or Spec — and reports findings without fixing them. Dispatched explicitly by /code-review — it works to a contract decided before it starts, so it is not a general coding agent.

• validator

  Checks the Spec draft /to-spec has just written — corrects facts in the draft file and returns the report. Dispatched explicitly by /to-spec — it works to a contract decided before it starts, so it is not a general coding agent.

• verifier

  Verifies one Iteration of an /implement run — checks the change against the Spec, runs the build and the whole test suite, runs the Spec's Hand checks, and measures its Stop rules. Dispatched explicitly by /implement — it works to a contract decided before it starts, so it is not a general coding ag

Similar plugins