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 to apply, and where domain documentation lives. Without per-repo configuration, these skills guess wrong or create duplicate labels and misplaced 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 proposing changes. - Three-decision configuration: Walks the user through choosing an issue tracker (GitHub, GitLab, local markdown, or other), mapping 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 seed files under docs/agents/ (issue-tracker.md, triage-labels.md, domain.md). - Use Case: After cloning a repo that uses GitLab issues and custom label names, run this skill once so the triage skill applies the correct labels and the diagnose skill reads the right CONTEXT.md files. ## Quick Start Ask the agent to run the setup-matt-pocock-skills skill to configure the issue tracker, triage labels, and domain docs for this repository.
