What problem does it solve? Engineering skills like to-issues, triage, 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 misplaced files. ## Core Features & Use Cases - Repo exploration: Inspects git remotes, existing AGENTS.md/CLAUDE.md, CONTEXT.md, ADR directories, and .scratch/ to understand the current state before writing anything. - Guided three-decision setup: Walks the user through choosing an issue tracker (GitHub via gh, GitLab via glab, local markdown under .scratch/, or a custom workflow), mapping the five canonical triage label roles, and confirming single-context vs multi-context domain docs. - Scaffolded output: Writes an ## Agent skills block into the existing CLAUDE.md or AGENTS.md plus docs/agents/issue-tracker.md, docs/agents/triage-labels.md, and docs/agents/domain.md from seed templates. - Use Case: After cloning a repo that uses GitLab instead of GitHub, run this skill so triage applies the correct labels via glab and diagnose reads the right CONTEXT.md files. ## Quick Start Ask the agent to run the setup-matt-pocock-skills skill to configure this repository's issue tracker, triage labels, and domain docs for the engineering skills.
