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 label vocabulary to use, and where domain documentation (CONTEXT.md, ADRs) resides. This Skill scaffolds that per-repo configuration once, so the other skills work correctly from first use. ## 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, writing the choice to docs/agents/issue-tracker.md. - Triage label vocabulary: Writes the five canonical triage roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) or user-provided overrides to docs/agents/triage-labels.md, only when the triage skill is installed. - Domain doc layout: Configures single-context (root CONTEXT.md + docs/adr/) or multi-context (CONTEXT-MAP.md with per-context docs) layouts based on detected monorepo signals. - Use Case: After cloning a repo that uses GitHub Issues, run this Skill once; it inspects the git remote, confirms choices with you, then writes the docs/agents/*.md files and an "## Agent skills" block into CLAUDE.md or AGENTS.md. ## Quick Start Ask the assistant to run the setup-matt-pocock-skills skill to configure this repository's issue tracker, triage labels, and domain docs for the engineering skills.
