5c3c49df1a
Move the map off a local Markdown file and onto the repo's configured issue tracker. The map is a single wayfinder:map issue whose tickets are its child issues — one shared URL the team can watch and comment on. Blocking, claiming (wayfinder:claimed), and the frontier query use native tracker semantics; a session loads the map at low resolution (Notes + per-closed-ticket context pointers + Fog prose) and zooms into tickets on demand. Per-tracker mechanics live behind the docs/agents/issue-tracker.md pointer, so setup-matt-pocock-skills seeds a "Wayfinding operations" section for GitHub, GitLab, and local-markdown; absent that doc, Wayfinder defaults to local-markdown. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| ask-matt | ||
| code-review | ||
| codebase-design | ||
| diagnosing-bugs | ||
| domain-modeling | ||
| grill-with-docs | ||
| implement | ||
| improve-codebase-architecture | ||
| prototype | ||
| resolving-merge-conflicts | ||
| setup-matt-pocock-skills | ||
| tdd | ||
| to-issues | ||
| to-prd | ||
| triage | ||
| README.md | ||
Engineering
Skills I use daily for code work.
User-invoked
Reachable only when you type them (disable-model-invocation: true).
- ask-matt — Ask which skill or flow fits your situation. A router over the user-invoked skills in this repo.
- grill-with-docs — Grilling session that also builds your project's domain model, sharpening terminology and updating
CONTEXT.mdand ADRs inline. - triage — Move issues through a state machine of triage roles.
- improve-codebase-architecture — Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
- setup-matt-pocock-skills — Configure this repo for the engineering skills (issue tracker, triage labels, domain doc layout). Run once per repo.
- to-issues — Break any plan, spec, or PRD into independently-grabbable issues using vertical slices.
- to-prd — Turn the current conversation into a PRD and publish it to the issue tracker.
Model-invoked
Model- or user-reachable (rich trigger phrasing so the model can reach for them).
-
prototype — Build a throwaway prototype to answer a design question: a runnable terminal app for state/logic, or several toggleable UI variations.
-
diagnosing-bugs — Disciplined diagnosis loop for hard bugs and performance regressions: reproduce → minimise → hypothesise → instrument → fix → regression-test.
-
tdd — Test-driven development with a red-green-refactor loop. Builds features or fixes bugs one vertical slice at a time.
-
domain-modeling — Actively build and sharpen a project's domain model — challenge terms, stress-test with scenarios, update
CONTEXT.mdand ADRs inline. -
codebase-design — Shared discipline and vocabulary for designing deep modules: small interfaces, clean seams, testable through the interface.
-
code-review — Two-axis review of the diff since a fixed point: Standards (does it follow the repo's coding standards, plus a Fowler smell baseline?) and Spec (does it faithfully implement the originating issue/PRD?), run as parallel sub-agents.