tt-a1i/matt-skills-with-to-goal

43 agent skills in one repository, published by tt-a1i. One command installs the lot; each skill also has its own page below.

1. ask-matt

   Ask which skill or flow fits your situation. A router over the skills in this repo.

2. claude-handoffBuilding agents

   Hand the current conversation off to a fresh background agent that picks up the work immediately.

3. code-reviewReview & testing

   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?). 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\".

4. codebase-design

   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.

5. diagnosing-bugsReview & testing

   Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.

6. domain-modelingWriting code

   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.

7. execute-spec-in-fork

   Orchestrate approved, bounded work through a same-directory Codex App fork: create and name the execution task, ask it to run spec-executor, route decisions through Codex Task Messenger, validate the returned receipt, and archive a completed child. The source may come from any planning workflow. Requires Codex App task tools and codex-task-messenger.

8. git-guardrails-claude-code

   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.

9. goal-crafterBuilding agents

   Draft a verifiable goal prompt from an idea or task. Use when the user asks for a goal, completion criteria, or a prompt to hand to another agent; this skill writes the goal rather than executing or scheduling it.

10. grill-me

    A relentless interview to sharpen a plan or design.

11. grill-with-docs

    A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.

12. grilling

    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.

13. handoff

    Compact the current conversation into a portable handoff document, with an optional live clarification path for compatible Codex tasks.

14. implementWriting code

    Implement a piece of work based on a spec or set of tickets.

15. implement-specWriting code

    Implement the result of /to-spec and /to-tickets in code.

16. improve-codebase-architecture

    Scan a codebase for deepening opportunities, present them as a report — HTML on request — then grill through whichever one you pick.

17. loop-me

    Grill me about specs for the workflows I want to build, within this workspace.

18. migrate-to-shoehornWriting code

    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.

19. pr

    Use when writing a PR body.

20. prototypeWriting code

    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.

21. researchResearch

    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.

22. resolving-merge-conflicts

    Use when you need to resolve an in-progress git merge/rebase conflict.

23. retro

    Conduct a retrospective on a coding session.

24. roundtableData & analysis

    Convene a roundtable of sub-agents that debate a decision or proposal from opposing perspectives — parallel independent statements, anonymous cross-review, then a chaired verdict reporting consensus and dissent.

25. scaffold-exercisesReview & testing

    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.

26. setup-matt-pocock-skillsDesign

    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.

27. setup-pre-commit

    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.

28. setup-ts-deep-modulesWriting code

    Wire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files. User-invoked.

29. spec-executor

    Execute approved, bounded work in an isolated implementation conversation and return a structured evidence receipt. Use with inherited history or an explicitly identified source; no particular planning, testing, or review skill is required.

30. tddReview & testing

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

31. teach

    Teach the user a new skill or concept, within this workspace.

32. to-goal

    Turn approved planning evidence or partially completed work into a portable, verifiable execution goal. Use when work needs to cross sessions, people, agents, or harnesses; no other skill or tracker setup is required.

33. to-questionnaire

    Turn a decision you can't fully answer into a questionnaire for someone else to fill in.

34. to-spec

    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.

35. to-tickets

    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 tracker).

36. triageBuilding agents

    Move issues and external PRs through a state machine of triage roles, categorise, verify, grill if needed, and write agent-ready briefs.

37. wait-what

    Stop. That last message did not land: re-pitch it.

38. wayfinderBuilding agents

    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.

39. wizardDeploy & operate

    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 migration or cutover. Don't invoke this for steps the agent can perform itself.

40. writing-beats

    Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.

41. writing-for-agents

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

42. writing-fragments

    Writing, explore: mine raw fragments, no structure yet.

43. writing-shape

    Writing, exploit: shape raw material into an article, paragraph by paragraph.