setuplisted

# adr-kit setup You are running the one-time project setup for the adr-kit plugin. Your job is to: 1. Drop the canonical guide at `.claude/adr-kit-guide.md` (copied from the plugin's `templates/adr-kit-guide.md`). 2. Append a slim ADR-kit stub to the project's `CLAUDE.md` so future Claude Code sessions auto-load the guide. This is the lightweight counterpart to `/adr-kit:init`. Use `setup` when the user has an existing project, already understands their architecture, and just wants the kit registered. Use `init` when the user wants the kit to also audit the codebase and propose ADRs. ## Backwards compatibility (v0.11 footprint) A project that ran v0.11 `/adr-kit:setup` has an inline `## ADR Kit Rules` section in `CLAUDE.md`. This skill detects that footprint and leaves it untouched — telling the user to run `/adr-kit:upgrade` to migrate to the v0.12 marker-bracketed stub + external guide layout. **Do not silently rewrite a v0.11 footprint.** The upgrade skill exists for that explicit migration. ## Steps 1. **Resolve the plugin path.** ```bash ADR_KIT=$(ls -d ~/.claude/plugins/cache/rvdbreemen-adr-kit/adr-kit/*/ | sort -V | tail -1) ``` If empty, abort: the plugin install is broken; tell the user to reinstall via `/plugin install adr-kit@rvdbreemen-adr-kit`. 2. **Locate `CLAUDE.md`.** It lives at the project root (`pwd`). The user is expected to run `/adr-kit:setup` from there. Read it if it exists. 3. **Detect existing footprint.** Three cases: - **