Matt Pocock/to-questionnaire
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Published by Matt Pocock
AIPM publisher
These public skills were imported from their linked source repositories. This publisher has not claimed the AIPM account yet.
Account verification confirms account control. It does not guarantee that every package is safe.
33 skills
Turn a decision you can't fully answer into a questionnaire for someone else to fill in.
Published by Matt Pocock
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.
Published by Matt Pocock
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.
Published by Matt Pocock
Use when writing a PR body.
Published by Matt Pocock
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.
Published by Matt Pocock
Implement the result of /to-spec and /to-tickets in code.
Published by Matt Pocock
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...
Published by Matt Pocock
Stop. That last message did not land: re-pitch it.
Published by Matt Pocock
Conduct a retrospective on a coding session.
Published by Matt Pocock
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.
Published by Matt Pocock
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
Published by Matt Pocock
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.
Published by Matt Pocock
Ask which skill or flow fits your situation. A router over the skills in this repo.
Published by Matt Pocock
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
Published by Matt Pocock
Generate 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, or running a one-off mig...
Published by Matt Pocock
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...
Published by Matt Pocock
Implement a piece of work based on a spec or set of tickets.
Published by Matt Pocock
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...
Published by Matt Pocock
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
Published by Matt Pocock
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
Published by Matt Pocock
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...
Published by Matt Pocock
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
Published by Matt Pocock
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.
Published by Matt Pocock
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.
Published by Matt Pocock
Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.
Published by Matt Pocock
Teach the user a new skill or concept, within this workspace.
Published by Matt Pocock
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.
Published by Matt Pocock
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
Published by Matt Pocock
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Published by Matt Pocock
A relentless interview to sharpen a plan or design.
Published by Matt Pocock
Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.
Published by Matt Pocock
Compact the current conversation into a handoff document for another agent to pick up.
Published by Matt Pocock
>
Published by Matt Pocock