domains / agent-tooling / repo-agent-skill-setup / setup-matt-pocock

setup-matt-pocock

Skill card

combined

The two copies are the same setup workflow but they disagree on the canonical domain-doc filenames and on how the triage section is gated. The mattpocock/skills copy uses GLOSSARY.md/GLOSSARY-MAP.md and skips Section B entirely when the triage skill is not installed, while the sickn33 copy uses CONTEXT.md/CONTEXT-MAP.md and always asks for triage label overrides. Crowning one would hide a real alternative, so the combined instruction preserves both variants and flags the conflicts.

Repositories

Other copies

Combined skill

---
name: setup-matt-pocock-skills
description: "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."
disable-model-invocation: true
---

# 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 the domain glossary/context file 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:

- `git remote -v` and `.git/config`: is this a GitHub repo? Which one?
- `AGENTS.md` and `CLAUDE.md` at the repo root: does either exist? Is there already an `## Agent skills` section in either?
- Domain doc files at the repo root: `GLOSSARY.md` / `GLOSSARY-MAP.md` (mattpocock/skills) or `CONTEXT.md` / `CONTEXT-MAP.md` (sickn33/agentic-awesome-skills)
- `docs/adr/` and any `src/*/docs/adr/` directories
- `docs/agents/`: does this skill's prior output already exist?
- `.scratch/`: a sign that a local-markdown issue tracker convention is already in use
- 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 in the mattpocock/skills variant.
- Monorepo signals (mattpocock/skills variant): a `pnpm-workspace.yaml`, a `workspaces` field in `package.json`, or a populated `packages/*` with its own `src/`. Their absence means single-context.

### 2. Present findings and ask

Summarise what's present and what's missing. Then take the sections in order. One section, one answer, then 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.

**Section A: Issue tracker.**

> Explainer: The "issue tracker" is where issues live for this repo. Skills like `to-tickets`/`to-issues`, `triage`, and `to-spec`/`to-prd` read from and write to it. They need to know whether to call `gh issue create`, write a markdown file under `.scratch/`, or follow some other workflow you describe. Pick the place you actually 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** (Jira, Linear, etc.): 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`.

PRs as a request surface:
- mattpocock/skills variant: the GitHub and GitLab templates carry a "PRs as a request surface" flag, defaulted **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.
- sickn33/agentic-awesome-skills variant: if the user picked GitHub or GitLab, ask one follow-up: "PRs as a request surface — yes / no (default: no)." Record the answer in `docs/agents/issue-tracker.md`. For local-markdown and other trackers, skip this question.

**Section B: Triage label vocabulary.**

mattpocock/skills variant: Skip this section entirely if the `triage` skill isn't installed, since 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, 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 if the user says no, collect the overrides so `triage` applies existing labels instead of creating duplicates.

sickn33/agentic-awesome-skills variant: Always present the five canonical roles and ask the user if they want to override any. The five canonical roles are: `needs-triage` (maintainer needs to evaluate), `needs-info` (waiting on reporter), `ready-for-agent` (fully specified, AFK-ready), `ready-for-human` (needs human implementation), `wontfix` (will not be actioned). Default: each role's string equals its name. If their issue tracker has no existing labels, the defaults are fine.

**Section C: Domain docs.**

mattpocock/skills variant: Default to **single-context** (one `GLOSSARY.md` + `docs/adr/` at the repo root). This fits almost every repo; write it without asking. Offer **multi-context** (a root `GLOSSARY-MAP.md` pointing to per-context `GLOSSARY.md` files) only when exploration found monorepo signals. Then confirm which layout they want.

sickn33/agentic-awesome-skills variant: Confirm the layout: **Single-context** — one `CONTEXT.md` + `docs/adr/` at the repo root. Most repos are this. **Multi-context** — `CONTEXT-MAP.md` at the root pointing to per-context `CONTEXT.md` files (typically a monorepo).

### 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 Section B ran)

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 one 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:

```markdown
## 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 Section B ran. When it didn't, both are omitted.

## Conflicts

- **mattpocock/skills** uses `GLOSSARY.md` and `GLOSSARY-MAP.md` for domain docs; **sickn33/agentic-awesome-skills** uses `CONTEXT.md` and `CONTEXT-MAP.md`.
- **mattpocock/skills** skips Section B entirely when the `triage` skill is not installed; **sickn33/agentic-awesome-skills** always asks the user whether to override the five canonical triage labels.
- **mattpocock/skills** lists monorepo signals (`pnpm-workspace.yaml`, `workspaces` field, `packages/*`) to decide whether to offer multi-context; **sickn33/agentic-awesome-skills** does not list those signals and simply confirms single- vs multi-context.
- **mattpocock/skills** references skills `to-tickets`, `triage`, and `to-spec`; **sickn33/agentic-awesome-skills** references `to-issues`, `triage`, `to-prd`, and `qa`.
- **mattpocock/skills** keeps the PRs-as-a-request-surface flag defaulted off and does not raise it; **sickn33/agentic-awesome-skills** asks the user directly when GitHub or GitLab is chosen.