# Matt Pocock Skills Routing

Source: [mattpocock/skills](https://github.com/mattpocock/skills/tree/main), inspected at commit `8515a080a74dbcf5019a1a78efc24b5fcafb36b8`.

## Installed Engineering Skills

The active engineering skills are installed in the user Codex skill root and available after Codex reloads its skill inventory:

- `ask-matt`: route a task to the right Matt Pocock flow.
- `grill-with-docs`: stress-test an idea while maintaining project domain notes.
- `codebase-design`: design deep modules, interfaces, seams, adapters, locality, and leverage.
- `domain-modeling`: sharpen domain terms and record hard-to-reverse decisions.
- `diagnosing-bugs`: build a tight repro loop before fixing hard bugs or performance regressions.
- `tdd`: use red-green-refactor for feature slices and bug fixes.
- `code-review`: review a diff on standards and spec axes.
- `improve-codebase-architecture`: find deepening opportunities and architecture friction.
- `prototype`: answer a design question with throwaway logic or UI.
- `research`: gather primary-source facts into cited Markdown.
- `resolving-merge-conflicts`: resolve merge/rebase conflicts by preserving both intents.
- `to-prd`: synthesize current context into a PRD.
- `to-issues`: split a PRD or plan into independent vertical slices.
- `implement`: implement a PRD or issue using TDD and review.
- `triage`: classify and prepare incoming issues or PRs.
- `setup-matt-pocock-skills`: upstream setup flow; this repo uses the local setup files in `docs/agents/` instead.

Already-installed productivity companions:

- `grill-me`, `grilling`, and `handoff` are already present in the user Codex skill root. Do not reinstall or overwrite them unless explicitly updating the skill source.

Not default-installed for this project:

- Deprecated, personal, and in-progress skills from the source repo.
- Misc skills such as Claude-only git guardrails, pre-commit setup, exercise scaffolding, and shoehorn migration, unless a future task explicitly targets that workflow.

## Autonomous Use Override

Matt Pocock skills often say to ask the user for confirmation. In this project, do not ask the user for routine skill-routing, seam, issue-breakdown, architecture, tracker, or setup decisions.

Instead:

1. Answer the question from `AGENTS.md`, `zonegaze/memory/README.md`, `zonegaze/memory/project-map.md`, relevant operating-model docs, source code, tests, and existing task trackers.
2. When a second opinion is useful, ask another agent or run a focused internal review instead of interrupting the user.
3. Treat the working agent as the decision owner. Prefer the best technically defensible path over the shortest path, document the assumption, and continue.
4. Ask the user only for hard blockers: missing secrets, destructive/live data risk, paid or free-tier dependency requests, unclear external-send target, or a decision that cannot be safely inferred from project context.

## Project Routing

- Use `ask-matt` as an internal router when the task shape is unclear.
- Use `grill-with-docs` or `grilling` to pressure-test large plans, but resolve questions agent-side using the autonomous override.
- Use `codebase-design` for SDK/library/API shape, reusable modules, deep interfaces, seams, adapters, and testability.
- Use `domain-modeling` when terminology, product concepts, or hard-to-reverse architectural decisions need sharpening.
- Use `diagnosing-bugs` with the existing `superpowers:systematic-debugging` skill for hard bugs, regressions, flakes, and performance problems.
- Use `tdd` for concrete feature or bug slices where a meaningful seam exists.
- Use `code-review` for large, risky, or user-requested reviews. Keep the project review stance: findings first, severity ordered, file/line grounded.
- Use `improve-codebase-architecture` for architecture-health passes and deepening opportunities. Put generated reports or screenshots under `project-testing/`, not random repo folders.
- Use `prototype` only for throwaway exploration. Mark prototypes clearly, keep them bounded, and delete or absorb them before task closeout.
- Use `research` when current API/library/platform facts are needed. Follow the ChatGPT `ZoneGaze Matrix` project workflow in `zonegaze/memory/agent-operating-model/04-upstreams-open-source-and-dependencies.md`, then verify official docs, source code, specs, license files, pricing pages, or first-party references before acting.
- Use `to-prd`, `to-issues`, and `implement` for substantial multi-session work. Prefer local `zonegaze/memory/` trackers over GitHub issues unless the user explicitly asks for GitHub issue writes.
- Use `triage` only when the task explicitly involves issue/PR intake or a backlog. Local tracker triage is the default.
- Use `resolving-merge-conflicts` for merge/rebase conflicts, while preserving this repo's `development` integration and no-force-push rules.

## Source Evaluation

- Source class: trusted public repository.
- License: MIT.
- Applied decision: active engineering skills installed; duplicate productivity skills left as-is; deprecated/personal/in-progress/misc skills excluded from default routing.
- Compatibility patch: installed skills with upstream `disable-model-invocation` frontmatter were adjusted locally to store that flag under `metadata`, which Codex validation accepts.
