What problem does it solve? Engineering skills like triage, to-tickets, and wayfinder need to know where issues live, which triage labels to apply, 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: Records whether issues live in GitHub (gh CLI), GitLab (glab CLI), local markdown under .scratch/, or another tracker, written 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 label strings your tracker actually uses. - Domain doc layout: Configures single-context (CONTEXT.md + docs/adr/) or multi-context (CONTEXT-MAP.md with per-context docs) layouts and consumer rules. - Use Case: After installing the engineering skills on a GitHub repo, run this setup once to generate docs/agents/*.md files and an Agent skills section in CLAUDE.md or AGENTS.md, so triage and ticketing skills work immediately. ## 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.
