What problem does it solve? Engineering skills like triage, to-tickets, and to-spec need to know where a repo's 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 workflow, writing the choice to docs/agents/issue-tracker.md. - 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 for monorepos, and updates CLAUDE.md or AGENTS.md with an Agent skills section. - Use Case: After installing a set of engineering skills in a GitHub-backed repo, run this Skill once to generate docs/agents/issue-tracker.md, triage-labels.md, and domain.md so subsequent triage and ticket-creation runs use the correct conventions. ## 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.
