What problem does it solve? Engineering skills like triage, to-issues, and diagnose need to know where a repo's issues live, which label strings to apply, and where domain documentation resides. Without per-repo configuration, they guess wrong or create duplicate labels and files. ## Core Features & Use Cases - Guided repo exploration: Inspects git remotes, existing AGENTS.md/CLAUDE.md, CONTEXT.md, docs/adr/, and .scratch/ to detect the current state before writing anything. - Three-decision interview: Walks the user through issue tracker choice (GitHub via gh, GitLab via glab, local markdown under .scratch/, or other), triage label vocabulary mapping for five canonical roles, and single-context vs multi-context domain docs layout. - Scaffolded output: Writes an ## Agent skills block into the existing CLAUDE.md or AGENTS.md plus seed docs under docs/agents/ (issue-tracker.md, triage-labels.md, domain.md) from bundled templates. - Use Case: After cloning Matt Pocock's engineering skills into a repo, run this once so triage applies your actual label strings and to-issues publishes to the right tracker instead of assuming defaults. ## 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.
