What problem does it solve? Engineering skills like triage, to-tickets, and to-spec need to know where a repo's issues live, which label vocabulary 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 repo's actual label strings in docs/agents/triage-labels.md. - Domain doc layout: Records single-context or multi-context layout for CONTEXT.md and ADR files in docs/agents/domain.md, plus an Agent skills block in CLAUDE.md or AGENTS.md. - Use Case: After installing the engineering skills in a GitHub-backed repo, run this setup once to generate the docs/agents configuration files so triage and ticket-creation skills operate against the correct tracker and labels. ## Quick Start Ask the agent to run the setup-matt-pocock-skills setup to configure this repository's issue tracker, triage labels, and domain docs for the engineering skills.
