What problem does it solve? Engineering skills like triage, to-issues, and diagnose need to know where a repo tracks issues, which triage label strings it uses, and where its domain documentation lives. Without that per-repo configuration, those skills guess wrong or create duplicate labels and files. ## Core Features & Use Cases - Guided repo exploration: Inspects git remotes, AGENTS.md/CLAUDE.md, CONTEXT.md, docs/adr/, and .scratch/ to detect the current setup before asking questions. - Three decision walkthroughs: Walks the user through issue tracker choice (GitHub, GitLab, local markdown, or other), triage label vocabulary mapping, and single-context vs multi-context domain docs. - Scaffolded configuration files: Writes an ## Agent skills block into the existing AGENTS.md or CLAUDE.md plus docs/agents/issue-tracker.md, triage-labels.md, and domain.md from seed templates. - Use Case: After cloning a repo that uses GitLab issues and custom label names, run this skill once so the triage and to-issues skills apply the correct labels via the glab CLI instead of assuming GitHub defaults. ## Quick Start Use the setup-matt-pocock-skills skill to configure this repository's issue tracker, triage labels, and domain docs for the engineering skills.