What problem does it solve? Engineering skills like triage, ticket creation, and implementation need to know where a repository tracks issues, which label strings it uses, and where domain docs live. This Skill performs that one-time per-repository setup so every other engineering skill reads consistent configuration instead of guessing. ## Core Features & Use Cases - Issue Tracker Setup: Detects the repository's remote and configures GitHub (gh CLI), GitLab (glab CLI), local markdown files under .scratch/, or a custom tracker workflow. - Label Vocabulary Mapping: Writes a mapping from canonical triage, type, and lifecycle roles (needs-triage, ready-for-agent, in-progress, etc.) to the label strings the tracker actually uses. - Domain Docs Layout: Configures single-context (CONTEXT.md plus docs/adr/) or multi-context (CONTEXT-MAP.md) layouts with consumer rules for engineering skills. - Use Case: After cloning a new project, run this Skill once; it explores the repo, confirms choices with you, then writes docs/agents/issue-tracker.md, triage-labels.md, and domain.md plus an Agent skills block in CLAUDE.md or AGENTS.md. ## Quick Start Ask the agent to run the setup-tracker skill to configure this repository's issue tracker, labels, and domain docs before using other engineering skills.