What problem does it solve? Engineering skills like triage, to-tickets, and to-spec need to know where 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 your tracker actually uses. - Domain doc layout: Records single-context (one CONTEXT.md plus 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 inspects git remotes and existing CLAUDE.md/AGENTS.md files, confirms choices with you, then writes docs/agents/*.md and an Agent skills block so triage and ticketing skills work immediately. ## 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.
