What problem does it solve? Engineering skills like triage, to-tickets, and to-spec need to know where issues live, which label vocabulary to use, and where domain docs reside. 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 by the user. - Triage label vocabulary: Writes the five canonical triage roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) or custom overrides into docs/agents/triage-labels.md when the triage skill is installed. - Domain doc layout: Records single-context (CONTEXT.md + docs/adr/) or multi-context (CONTEXT-MAP.md with per-context docs) conventions for monorepos. - Use Case: After cloning a repo that uses GitHub Issues, run this Skill once; it explores the repo, confirms choices with you, then writes docs/agents/*.md files and an '## Agent skills' block into 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.
