What problem does it solve? Engineering skills like triage, to-tickets, and wayfinder need to know where issues live, which label vocabulary to apply, and where domain documentation resides. This Skill scaffolds that per-repo configuration once, so every other skill reads consistent conventions 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 repo's actual label strings, only 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) structure for monorepos. - Use Case: After cloning a repo and installing the engineering skills, run this once to generate docs/agents/*.md files and an Agent skills section in CLAUDE.md or AGENTS.md that all other skills consume. ## Quick Start Ask the agent to run the setup skill to configure this repository's issue tracker, triage labels, and domain docs for the engineering skills.