What problem does it solve? Engineering skills like triage, to-tickets, and wayfinder need to know where issues live, which label vocabulary to apply, and where domain documentation resides. Without per-repo configuration, these skills guess at conventions and produce inconsistent results. This skill scaffolds that configuration once, before first use. ## Core Features & Use Cases - Issue tracker setup: Records whether issues live in GitHub (gh CLI), GitLab (glab CLI), local markdown under .scratch/, or another tracker, 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. - Domain doc layout: Configures single-context (CONTEXT.md + docs/adr/) or multi-context (CONTEXT-MAP.md with per-context docs) layouts and consumer rules. - Use Case: After installing the engineering skills into a GitHub repo, run this setup once to generate docs/agents/*.md files and an Agent skills block in CLAUDE.md or AGENTS.md so every other skill reads consistent 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.