setup-matt-pocock-skills

name	setup-matt-pocock-skills
description	Configure this repo for the engineering skills by setting up its issue tracker, triage label vocabulary, and domain doc layout. Run once before first use of the other engineering skills.
license	MIT
metadata	{"tags":"catalog,configuration,workflow","groups":"matt-workflow","invocation":"user","source":"https://github.com/mattpocock/skills@84fdeffd12f2ee307994d1eb6feb48173b6e0502:skills/engineering/setup-matt-pocock-skills"}

Setup Matt Pocock's skills

Scaffold the per-repo configuration that the engineering skills assume:

• Issue tracker. Where issues live (GitHub by default; local markdown is also supported out of the box)
• Triage labels. The strings used for the five canonical triage roles
• Domain docs. Where CONTEXT.md and ADRs live, and the consumer rules for reading them

This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.

Process

1. Explore

Look at the current repo to understand its starting state. Read whatever exists; don't assume:

• Check git remote -v and .git/config. Is this a GitHub repo? Which one?
• Check AGENTS.md and CLAUDE.md at the repo root. Does either exist? Does either already have an ## Agent skills section?
• CONTEXT.md and CONTEXT-MAP.md at the repo root
• docs/adr/ and any src/*/docs/adr/ directories
• Check docs/agents/ for this skill's prior output.
• Treat .scratch/ as a sign that the repo already uses a local Markdown issue tracker.
• Is the triage skill installed? (a triage skill folder alongside this one, or triage in your available skills.) This decides whether Section B runs at all.
• Check for monorepo signals: a pnpm-workspace.yaml, a workspaces field in package.json, or a populated packages/* with its own src/. Present this option only in a genuinely large multi-package repo. Their absence means single-context, which fits almost every repo.

2. Present findings and ask

Summarise what's present and what's missing. Then take the sections in order. Ask one section, get one answer, and continue to the next.

Lead each section with the recommended answer so the user can accept it in a word. Give a one-line explainer only when the choice genuinely branches; skip the section entirely when exploration already settled it (Section B when triage isn't installed, Section C when there's no monorepo).

Section A: issue tracker

Explainer: The "issue tracker" is where issues live for this repo. Skills like to-tickets, triage, and to-spec read from and write to it. They need to know whether to call gh issue create, write a Markdown file under .scratch/, or follow another workflow you describe. Pick the place you actually use to track work for this repo.

Default posture: these skills were designed for GitHub. If a git remote points at GitHub, propose that. If a git remote points at GitLab (gitlab.com or a self-hosted host), propose GitLab. Otherwise (or if the user prefers), offer:

• GitHub. Issues live in the repo's GitHub Issues (uses the gh CLI)
• GitLab. Issues live in the repo's GitLab Issues (uses the glab CLI)
• Local Markdown. Issues live as files under .scratch/<feature>/ in this repo (good for solo projects or repos without a remote)
• Other. For Jira, Linear, or another tracker, ask the user to describe the workflow in one paragraph. The skill will record it as freeform prose.

Record the choice in docs/agents/issue-tracker.md. The GitHub and GitLab templates carry a "PRs as a request surface" flag that defaults off. Leave it off and don't raise it. A user who wants external PRs in the triage queue can flip the flag in the file later.

Section B: triage label vocabulary

Skip this section entirely if exploration showed that the triage skill isn't installed. An uninstalled skill needs no labels.

If it is installed, ask exactly one question:

Do you want to keep the default triage labels? (recommended: yes)

The defaults are the five canonical roles, with each label string equal to its name: needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix. On yes, write them as-is. Only collect overrides if the user says no, usually because their tracker already uses other names such as bug:triage for needs-triage. This lets triage apply existing labels instead of creating duplicates.

Section C: domain docs

Default to single-context with one CONTEXT.md and docs/adr/ at the repo root. This fits almost every repo; write it without asking.

Offer multi-context only when exploration found monorepo signals. This layout uses a root CONTEXT-MAP.md that points to per-context CONTEXT.md files. Confirm which layout the user wants.

3. Confirm and edit

Show the user a draft of:

• The ## Agent skills block to add to whichever of CLAUDE.md / AGENTS.md is being edited (see step 4 for selection rules)
• The contents of docs/agents/issue-tracker.md, docs/agents/domain.md, and docs/agents/triage-labels.md (the last only when triage is installed)

Let them edit before writing.

4. Write

Pick the file to edit:

• If CLAUDE.md exists, edit it.
• Else if AGENTS.md exists, edit it.
• If neither exists, ask the user which one to create. Don't pick for them.

Never create AGENTS.md when CLAUDE.md already exists, or vice versa. Always edit the file that's already there.

If an ## Agent skills block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.

The block:

## Agent skills

### Issue tracker

[one-line summary of where issues are tracked]. See `docs/agents/issue-tracker.md`.

### Triage labels

[one-line summary of the label vocabulary]. See `docs/agents/triage-labels.md`.

### Domain docs

[one-line summary of layout — "single-context" or "multi-context"]. See `docs/agents/domain.md`.

Include the ### Triage labels sub-block, and write docs/agents/triage-labels.md, only when triage is installed and Section B ran. When it isn't, both are omitted.

Then write the docs files using the seed templates in this skill folder as a starting point:

• issue-tracker-github.md configures the GitHub issue tracker.
• issue-tracker-gitlab.md configures the GitLab issue tracker.
• issue-tracker-local.md configures the local Markdown issue tracker.
• triage-labels.md maps labels when triage is installed.
• domain.md defines the domain doc layout and consumer rules.

For "other" issue trackers, write docs/agents/issue-tracker.md from scratch using the user's description.

5. Done

Tell the user the setup is complete and which engineering skills will now read from these files. Mention that they can edit docs/agents/*.md directly later. They only need to rerun this skill to switch issue trackers or restart from scratch.