What problem does it solve? Engineering skills like triage, to-tickets, and to-spec 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 from consistent, well-defined files 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, writing the conventions 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 actually used in the repo's tracker. - Domain Doc Layout: Defines single-context or multi-context layouts for CONTEXT.md, CONTEXT-MAP.md, and ADR directories, plus consumer rules for reading them. - Use Case: After installing a set of engineering skills into a repo, run this once to generate docs/agents/*.md files and an Agent skills section in CLAUDE.md or AGENTS.md so all downstream skills share the same configuration. ## Quick Start Ask the agent to set up this repository for the engineering skills by configuring the issue tracker, triage labels, and domain docs.
