What problem does it solve? Engineering skills like to-issues, triage, to-prd, and diagnose need to know where your repo tracks issues, which triage label strings you use, and where domain documentation lives. Without that per-repo configuration, these skills guess wrong or create duplicate labels and misplaced files. ## Core Features & Use Cases - Guided repo exploration: Inspects git remotes, existing AGENTS.md/CLAUDE.md, CONTEXT.md, docs/adr/, and .scratch/ to detect your current setup before proposing anything. - Three decision walkthroughs: Walks you through choosing an issue tracker (GitHub via gh, GitLab via glab, local markdown under .scratch/, or a custom workflow), mapping the five canonical triage labels, and confirming single-context vs multi-context domain docs. - Scaffolded output: Writes an ## Agent skills block into your existing CLAUDE.md or AGENTS.md plus seed files under docs/agents/ (issue-tracker.md, triage-labels.md, domain.md). - Use Case: After cloning Matt Pocock's engineering skills into a GitHub repo, run this once so triage applies your real label names and to-issues publishes via gh issue create instead of guessing. ## 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.
