--- name: red-setup working-mode: interactive description: >- The one authorized creator of a repo's `.red/` directory and the only way to enable RedSkills plugins (dev, memory, brain) in a project (ADR 0067). RedSkills hooks are installed globally on every agent but stay fully inert in any directory without a `.red/config.yaml` whose `plugins..enabled: true` opts that plugin in. This skill prompts which plugins to enable, creates `.red/`, writes the activation flags, and sets up `## Agent skills`/`## Development workflow` blocks in AGENTS.md/CLAUDE.md plus `.red/agents/`. Run to turn RedSkills on in a repo, to enable/disable a plugin, before first use of `to-tickets`, `to-spec`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, `zoom-out`, or `/go`, or if those skills appear to be missing context. disable-model-invocation: true --- # Setup RedSkills **Scaffold the per-repo configuration that the engineering skills assume — this skill is the only thing authorized to create `.red/`.** NEVER create `.red/` outside this skill — plugins stay fully inert in any directory whose `.red/config.yaml` is missing or lacks an explicit `plugins..enabled: true`. This is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write. ## Hot Path 1. **Explore first.** Inspect the repo state listed in [REFERENCE.md](./REFERENCE.md#explore-checklist); do not assume prior RedSkills setup is absent or current. 2. **Ask in sequence.** Walk the user through one setup section at a time. Keep the plugin-activation gate first, then continue through issue tracker, triage labels, domain docs, workflows, token efficiency, runtime launcher, required host binaries, execution daemon, statusline, config template and Validation moments, the Release standard, command guards, development workflow, and hook scripts. Use the exact section copy and choices in [INTERVIEW.md](./INTERVIEW.md). 3. **Confirm before writing.** Show the draft agent-skills block, generated agent docs, development-workflow changes, and any accepted command-guard policy before editing. See [WRITE-CONTRACT.md](./WRITE-CONTRACT.md#confirm-and-edit). 4. **Write under the no-clobber contract.** Never overwrite, rewrite, or reorder existing user-owned content except for the explicit surgical merges named in [WRITE-CONTRACT.md](./WRITE-CONTRACT.md#write). Use the existing-file selection rules, seed docs, workflow copy rules, plugin-activation merge, development-workflow injector, statusline wiring, and hook-script registration exactly as documented there. 5. **Sweep existing issues only after setup.** If open issues exist, group label backfill candidates and ask for one batch approval before editing labels. See [ISSUE-SWEEP.md](./ISSUE-SWEEP.md). 6. **Verify the session before recapping — installed is not loaded.** Check whether this session actually sees the enabled plugins' MCP tools, and report `installed and loaded` or `installed, reload needed` explicitly. See [WRITE-CONTRACT.md](./WRITE-CONTRACT.md#verify-the-session-sees-the-plugin). 7. **Report the files this run wrote and never committed — before the recap.** Name every path (`.red/config.yaml`, `.red/.gitignore`, `.red/hooks/**`), say they are uncommitted, offer the exact `git commit` and leave the decision with the user. See [WRITE-CONTRACT.md](./WRITE-CONTRACT.md#report-the-files-this-run-wrote-and-never-committed). 8. **Finish with the setup recap.** Tell the user which plugins are enabled here, carry the session verdict from step 6 into it, say `written, restart needed` when this run wrote the `statusLine` (a skipped write announces nothing — see [WRITE-CONTRACT.md](./WRITE-CONTRACT.md#write)), remind them that other directories stay inert until setup runs there too, point memory/brain users at their next init step, and route one-off concrete work through `/go`, backlog work through `/afk`, and parked issues through `/retake`. ## Hard Rules - **Only this skill may create `.red/`.** Creating `.red/` is authorized only by the plugin-activation decision; if the user enables no plugins, write nothing. - **The daemon's home is the daemon's.** This skill's `.red/` authority is repository-scoped. `~/.red/redskilled/` is operator-scoped, owned by `redskilled` (ADR 0130 Amendment 1), and provisioned by running `npx -y -p @reddb-io/red-skills@ red-skills-redskilled provision` — never by creating the directory here. Route per-machine status, ceilings, and lifecycle to `/redskilled`. - **Global hooks are inert by default.** A plugin block alone is not enough: each enabled plugin must have `plugins..enabled: true` in `.red/config.yaml` (ADR 0067). - **GitHub Issues only.** In reddb.io repos there is no local fallback and no supported alternate issue tracker. Stop if the repo has no GitHub remote. - **No clobbering.** Existing files are project state. Skip existing targets unless the referenced write contract explicitly names a surgical exception. - **Do not add generated setup files for the user — but never leave silently.** Do not `git add` `.red/config.yaml`, `.red/.gitignore`, or hook files written by this setup; the decision is the operator's. **A run that writes those files and says nothing about them is an unclosed cycle (#3106)**: it leaves the tree dirty by contract and the operator with no idea it did. Name them, offer the commit, run it only if asked. - **Workflow install is opt-in by lane.** Install only the workflows the user picked; standalone copy-installables keep their `red-*` filename, while reusable callers use `rs-*`. - **Command guards are offer-only.** The built-in dev worktree invariant comes from `plugins.dev.enabled: true`; do not write example `command_guard` rules unless the user explicitly accepts them. - **Validation commands are proposal-only.** Discover `test`, `typecheck`, `lint`, and `build` scripts from the repository's package manifests, show the exact proposed `plugins.dev.afk.validation` block, and leave fresh and existing configs untouched until the operator confirms it. - **Release configuration is proposal-only.** After Validation moments, collect the scheme, trigger, pre-release, and execution choices; detect and propose the Version surfaces; then leave `release.*` untouched in fresh and existing configs until the operator confirms the complete block. - **Never end on success while the session is blind.** A plugin enabled here is not a plugin loaded here: a host registers MCP servers at plugin load, so an install or update in THIS session leaves valid files on disk and zero tools in the session. Ending the recap on `✅ enabled` while the agent cannot call a single tool is what turns a one-line cure into a forensic investigation — say `installed, reload needed` and name `/reload-plugins`. - **ask-red maintenance rule.** Skill add, rename, removal, or flow changes require re-checking `../ask-red/SKILL.md` and updating its Coverage Inventory/routes. A progressive-disclosure-only extraction of this skill is not such a change; no router update is expected after re-checking. ## Reference Map - [REFERENCE.md](./REFERENCE.md) — setup scope, scaffold list, and exploration checklist. - [INTERVIEW.md](./INTERVIEW.md) — the full section-by-section user interview, including plugin activation, workflows, token efficiency, runtime launcher, statusline, config template, command guards, development workflow, and hook-script offers. - [WRITE-CONTRACT.md](./WRITE-CONTRACT.md) — confirmation draft requirements, no-clobber rules, file-selection rules, seed-doc writes, workflow installation, config merges, statusline wiring, hook writes, and final recap text. - [ISSUE-SWEEP.md](./ISSUE-SWEEP.md) — open-issue label backfill mechanics. - Existing seed/reference files: [issue-tracker-github.md](./issue-tracker-github.md), [triage-labels.md](./triage-labels.md), [domain.md](./domain.md), [config-template.yaml](./config-template.yaml), [WORKFLOWS.md](./WORKFLOWS.md), and [scripts/install-runtime-shim.sh](https://github.com/reddb-io/redskilled/blob/main/runtime/plugins/dev/skills/engineering/red-setup/scripts/install-runtime-shim.sh).