Setup Utarn Skills Yes

Setup Utarn's Skills

Scaffold the per-repo configuration that the engineering skills assume:

• Issue tracker — where issues live (GitHub by default; local markdown is also supported out of the box)
• Triage labels — the strings used for the five canonical triage roles
• Domain docs — where CONTEXT.md and ADRs live, and the consumer rules for reading them

This is a prompt-driven skill, not a deterministic script. Explore, take the recommended default for every section — derived from what the repo itself implies — then write. No confirmation rounds.

Process

1. Explore

Look at the current repo to understand its starting state. Read whatever exists; don't assume:

• git 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 root
• docs/adr/ and any src/*/docs/adr/ directories
• docs/agents/ — does this skill's prior output already exist?
• .scratch/ — sign that a local-markdown issue tracker convention is already in use
• Is the triage skill installed? (a triage skill folder alongside this one, or triage in your available skills.) This decides whether Section B runs at all.
• Monorepo signals — a pnpm-workspace.yaml, a workspaces field in package.json, or a populated packages/* with its own src/. Present only in a genuinely large multi-package repo; their absence means single-context, which is almost every repo.

2. Present findings and accept the defaults

Summarise what's present and what's missing, then take each section's recommended default without asking. Show each choice in one line as you make it, so the final state is auditable. Skip a section entirely when exploration already settled it (Section B when triage isn't installed).

Section A — Issue tracker. Accept the default the remote implies:

• A git remote pointing at GitHub → GitHub (issues live in the repo's GitHub Issues, via the gh CLI)
• A git remote pointing at GitLab (gitlab.com or a self-hosted host) → GitLab (via the glab CLI)
• Anything else → local markdown (issues live as files under .scratch/<feature>/ in this repo)

Custom trackers (Jira, Linear, …) need a workflow description only the user can give — they are out of reach here; run the interactive /setup-utarn-skills for those.

Record the choice in docs/agents/issue-tracker.md. The GitHub and GitLab templates carry a "PRs as a request surface" flag, defaulted off — leave it off.

Section B — Triage label vocabulary. Skip this section entirely if the triage skill isn't installed (exploration told you) — an uninstalled skill needs no labels.

If it is installed, take the recommended answer: keep the default triage labels. They are the five canonical roles, each label string equal to its name: needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix. Write them as-is.

Section C — Domain docs. Take the default the repo shape implies: single-context — one CONTEXT.md + docs/adr/ at the repo root — unless exploration found monorepo signals, in which case multi-context (a root CONTEXT-MAP.md pointing to per-context CONTEXT.md files). Either way, write it without asking.

3. Draft

Draft, without waiting for edits — step 5 reports everything that was chosen:

• The ## Agent skills block to add to whichever of CLAUDE.md / AGENTS.md is being edited (see step 4 for selection rules)
• The contents of docs/agents/issue-tracker.md, docs/agents/domain.md, and docs/agents/triage-labels.md (the last only when triage is installed)

4. Write

Pick the file to edit:

• If CLAUDE.md exists, edit it.
• Else if AGENTS.md exists, edit it.
• If neither exists, create CLAUDE.md.

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:

## Agent skills

### Issue tracker

[one-line summary of where issues are tracked]. See `docs/agents/issue-tracker.md`.

### Triage labels

[one-line summary of the label vocabulary]. See `docs/agents/triage-labels.md`.

### Domain docs

[one-line summary of layout — "single-context" or "multi-context"]. See `docs/agents/domain.md`.

Include the ### Triage labels sub-block, and write docs/agents/triage-labels.md, only when triage is installed and Section B ran. When it isn't, both are omitted.

Then write the docs files using the seed templates in the setup-utarn-skills folder as a starting point:

• issue-tracker-github.md — GitHub issue tracker
• issue-tracker-gitlab.md — GitLab issue tracker
• issue-tracker-local.md — local-markdown issue tracker
• triage-labels.md — label mapping (only if triage is installed)
• domain.md — domain doc consumer rules + layout

5. Done

Tell the user the setup is complete and recap the defaults that were taken — tracker, triage labels, doc layout, and which file was edited — plus which engineering skills will now read from these files. Mention they can edit docs/agents/*.md directly later, and that a default that turned out wrong can be fixed by editing the file or re-running the interactive /setup-utarn-skills — re-running is otherwise only necessary to switch issue trackers or restart from scratch.