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 strings to apply, and where domain documentation (CONTEXT.md, ADRs) resides. This Skill scaffolds that per-repo configuration once, so the other skills work without repeated setup questions. ## Core Features & Use Cases - Issue tracker configuration: Detects GitHub or GitLab remotes and records the chosen tracker (GitHub, GitLab, local markdown under .scratch/, or a custom workflow) in docs/agents/issue-tracker.md. - Triage label vocabulary: Writes the five canonical triage roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) or custom overrides to docs/agents/triage-labels.md when the triage skill is installed. - Domain doc layout: Records single-context or multi-context (monorepo) layout with CONTEXT.md, CONTEXT-MAP.md, and ADR consumer rules in docs/agents/domain.md. - Use Case: After cloning a repo that uses GitHub Issues, run this Skill once; it inspects the repo, confirms choices with you, updates CLAUDE.md or AGENTS.md with an Agent skills block, and writes the docs/agents/ configuration files. ## 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.