What problem does it solve? Engineering skills like triage, to-tickets, and wayfinder need to know where a repo's issues live, which triage labels to apply, and where domain docs are stored. This Skill scaffolds that per-repo configuration once, so every other engineering skill reads from consistent, documented conventions 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 described in freeform prose. - Triage label vocabulary: Writes the five canonical triage roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) or maps them to the repo's existing label strings. - Domain doc layout: Records single-context (CONTEXT.md + docs/adr/) or multi-context (CONTEXT-MAP.md with per-context docs) layouts, plus consumer rules for reading ADRs and glossaries. - Use Case: After cloning a repo that uses GitHub Issues, run this Skill once; it inspects the repo, confirms choices with you, then writes docs/agents/issue-tracker.md, docs/agents/domain.md, and an Agent skills block in CLAUDE.md so all other engineering skills work immediately. ## Quick Start Ask the agent to set up this repository for the engineering skills by configuring the issue tracker, triage labels, and domain docs.
