What problem does it solve? Engineering skills like triage, to-tickets, and to-spec need to know where issues live, which triage labels to apply, and where domain documentation resides. This Skill scaffolds that per-repo configuration once, so every other engineering skill reads consistent settings instead of guessing. ## Core Features & Use Cases - Issue tracker setup: Detects the repo's remote and records whether issues live in GitHub (gh CLI), GitLab (glab CLI), local markdown under .scratch/, or a custom tracker described in freeform prose. - Triage label vocabulary: Maps the five canonical triage roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) to the label strings actually used in the repo's tracker. - Domain doc layout: Records single-context (CONTEXT.md + docs/adr/) or multi-context (CONTEXT-MAP.md with per-context docs) conventions, plus consumer rules for reading ADRs and glossaries. - Use Case: After installing the engineering skills into a GitHub repo, run this once to generate docs/agents/issue-tracker.md, docs/agents/triage-labels.md, docs/agents/domain.md, and an Agent skills block in CLAUDE.md or AGENTS.md. ## 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 before using the other engineering skills.
