setup-pococklisted

# 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 - **PRD / roadmap track model** _(optional)_ — a thin portfolio (`docs/roadmap.md`) of tracks, each backed by a PRD (`docs/prd/`) that maps to one issue grouping. Opt-in; works on top of any issue tracker above, or skip it entirely. 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? - `CONTEXT.md` and `CONTEXT-MAP.md` at the repo root - `docs/adr/` and any `src/*/docs/adr/` directories - `docs/agents/` — does this skill's prior output already exist? - `.scratch/` — sign that a local-markdown issue tracker convention is already in use ### 2. Present findings and ask Summarise what's present and what's missing. Then walk the user through the three decisions **one at a time** — present a section, get the user's