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 settings 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 tracker, 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 in docs/agents/triage-labels.md. - Domain doc layout: Records single-context or multi-context CONTEXT.md and ADR conventions in docs/agents/domain.md, and adds an Agent skills block to CLAUDE.md or AGENTS.md. - Use Case: After cloning a repo that uses GitHub Issues, run this Skill once; it inspects git remotes and existing docs, confirms choices with you, then writes the configuration files that triage and wayfinder will read on every subsequent run. ## Quick Start Ask the assistant to run the setup skill to configure this repository's issue tracker, triage labels, and domain docs for the engineering skills.
