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 resides. This Skill scaffolds that per-repo configuration once, so the other skills work correctly from the start. ## Core Features & Use Cases - Issue tracker setup: Detects the repo's remote and records whether issues live in GitHub, GitLab, local markdown under .scratch/, or another tracker, writing the choice to docs/agents/issue-tracker.md. - Triage label vocabulary: Records the five canonical triage roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) or custom overrides in docs/agents/triage-labels.md. - Domain doc layout: Configures single-context (CONTEXT.md + docs/adr/) or multi-context (CONTEXT-MAP.md with per-context docs) layouts in docs/agents/domain.md. - Use Case: After installing the engineering skills into a GitHub repo, run this Skill once to generate the ## Agent skills block in CLAUDE.md and the supporting docs/agents/ files, so triage and ticketing skills immediately know how to operate. ## Quick Start Ask the agent to set up this repository for the engineering skills by configuring the issue tracker, triage labels, and domain docs.