What problem does it solve? Engineering skills like triage, to-tickets, and to-spec need to know where issues live, which label vocabulary to apply, and where domain documentation resides. Without a one-time per-repo configuration, each skill would guess at tracker CLIs, label strings, and doc locations, producing inconsistent results. ## 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 another 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 whether the repo uses a single CONTEXT.md plus docs/adr/ or a multi-context CONTEXT-MAP.md layout, with consumer rules for reading them. - Use Case: After installing the engineering skills into a GitHub-backed repo, run this setup once to write docs/agents/issue-tracker.md, triage-labels.md, and domain.md, plus an Agent skills block in CLAUDE.md or AGENTS.md, so every other skill reads consistent configuration. ## 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.
