What problem does it solve? Engineering skills like to-tickets, triage, and to-spec need to know where issues live, which triage label vocabulary to use, 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 git remote and records whether issues live in GitHub Issues, GitLab Issues, local markdown under .scratch/, or another tracker, writing the choice to docs/agents/issue-tracker.md from seed templates. - 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 in docs/agents/triage-labels.md. - Domain docs layout: Records single-context (CONTEXT.md + docs/adr/) or multi-context (CONTEXT-MAP.md with per-context docs) layout rules in docs/agents/domain.md, and adds an ## Agent skills block to CLAUDE.md or AGENTS.md. - Use Case: After installing the engineering skill suite into a GitLab monorepo, run this Skill once to detect the remote, confirm the multi-context layout, and generate all configuration docs before using any other skill. ## Quick Start Set up this repository for the engineering skills by configuring its issue tracker, triage labels, and domain docs.