## Agent skills block in AGENTS.md/CLAUDE.md and docs/agents/ so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of to-issues, to-prd, triage, diagnose, tdd, improve-codebase-architecture, or zoom-out — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.\ndisable-model-invocation: trueScaffold the per-repo configuration that the engineering skills assume:
\nCONTEXT.md and ADRs live, and the consumer rules for reading themThis is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.
\nLook at the current repo to understand its starting state. Read whatever exists; don't assume:
\ngit remote -v and .git/config — is this a GitHub repo? Which one?AGENTS.md and CLAUDE.md at the repo root — does either exist? Is there already an ## Agent skills section in either?CONTEXT.md and CONTEXT-MAP.md at the repo rootdocs/adr/ and any src/*/docs/adr/ directoriesdocs/agents/ — does this skill's prior output already exist?.scratch/ — sign that a local-markdown issue tracker convention is already in useSummarise what's present and what's missing. Then walk the user through the three decisions one at a time — present a section, get the user's answer, then move to the next. Don't dump all three at once.
\nAssume the user does not know what these terms mean. Each section starts with a short explainer (what it is, why these skills need it, what changes if they pick differently). Then show the choices and the default.
\nSection A — Issue tracker.
\n\n\nExplainer: The \"issue tracker\" is where issues live for this repo. Skills like
\nto-issues,triage,to-prd, andqaread from and write to it — they need to know whether to callgh issue create, write a markdown file under.scratch/, or follow some other workflow you describe. Pick the place you actually track work for this repo.
Default posture: these skills were designed for GitHub. If a git remote points at GitHub, propose that. If a git remote points at GitLab (gitlab.com or a self-hosted host), propose GitLab. Otherwise (or if the user prefers), offer:
gh CLI)glab CLI).scratch/<feature>/ in this repo (good for solo projects or repos without a remote)Section B — Triage label vocabulary.
\n\n\nExplainer: When the
\ntriageskill processes an incoming issue, it moves it through a state machine — needs evaluation, waiting on reporter, ready for an AFK agent to pick up, ready for a human, or won't fix. To do that, it needs to apply labels (or the equivalent in your issue tracker) that match strings you've actually configured. If your repo already uses different label names (e.g.bug:triageinstead ofneeds-triage), map them here so the skill applies the right ones instead of creating duplicates.
The five canonical roles:
\nneeds-triage — maintainer needs to evaluateneeds-info — waiting on reporterready-for-agent — fully specified, AFK-ready (an agent can pick it up with no human context)ready-for-human — needs human implementationwontfix — will not be actionedDefault: each role's string equals its name. Ask the user if they want to override any. If their issue tracker has no existing labels, the defaults are fine.
\nSection C — Domain docs.
\n\n\nExplainer: Some skills (
\nimprove-codebase-architecture,diagnose,tdd) read aCONTEXT.mdfile to learn the project's domain language, anddocs/adr/for past architectural decisions. They need to know whether the repo has one global context or multiple (e.g. a monorepo with separate frontend/backend contexts) so they look in the right place.
Confirm the layout:
\nCONTEXT.md + docs/adr/ at the repo root. Most repos are this.CONTEXT-MAP.md at the root pointing to per-context CONTEXT.md files (typically a monorepo).Show the user a draft of:
\n## Agent skills block to add to whichever of CLAUDE.md / AGENTS.md is being edited (see step 4 for selection rules)docs/agents/issue-tracker.md, docs/agents/triage-labels.md, docs/agents/domain.mdLet them edit before writing.
\nPick the file to edit:
\nCLAUDE.md exists, edit it.AGENTS.md exists, edit it.Never create AGENTS.md when CLAUDE.md already exists (or vice versa) — always edit the one that's already there.
If an ## Agent skills block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.
The block:
\n## Agent skills\n\n### Issue tracker\n\n[one-line summary of where issues are tracked]. See `docs/agents/issue-tracker.md`.\n\n### Triage labels\n\n[one-line summary of the label vocabulary]. See `docs/agents/triage-labels.md`.\n\n### Domain docs\n\n[one-line summary of layout — \"single-context\" or \"multi-context\"]. See `docs/agents/domain.md`.\nThen write the three docs files using the seed templates in this skill folder as a starting point:
\nFor \"other\" issue trackers, write docs/agents/issue-tracker.md from scratch using the user's description.
Tell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit docs/agents/*.md directly later — re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.