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 apply, and where domain documentation resides. This Skill scaffolds that per-repo configuration once, so the other skills work without repeated manual setup. ## Core Features & Use Cases - Issue Tracker Configuration: Detects the repo's remote and 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 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) layouts based on monorepo signals. - Use Case: After installing the engineering skills into a GitHub repo, run this Skill once to generate docs/agents/*.md files and an Agent skills block in CLAUDE.md or AGENTS.md, so subsequent triage and ticket workflows know exactly where to read and write. ## Quick Start Ask the AI to run the setup skill to configure this repository's issue tracker, triage labels, and domain documentation layout for the engineering skills.
