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 vocabulary to use, and where domain documentation (CONTEXT.md, ADRs) resides. This Skill scaffolds that per-repo configuration once, so the other skills work correctly from the start. ## Core Features & Use Cases - Issue tracker setup: 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. - Domain doc layout: Configures single-context or multi-context layouts for CONTEXT.md and ADR directories, with consumer rules for reading them. - Use Case: After installing the engineering skills into 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 every subsequent skill invocation knows where to read and write. ## 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.
