conductor-setuplisted

# Skill: conductor-setup Configures a repo's full Conductor workspace lifecycle in `.conductor/settings.toml`: **setup** (runs after workspace creation), **run** (a menu of selectable, named targets instead of one auto-starting script), and **archive** (cleanup before a workspace is removed). See the [Conductor scripts reference](https://conductor.build/docs/reference/scripts). Work collaboratively: discover real commands, confirm choices, then write. **Never overwrite an existing script without asking. Do not commit, push, or open a PR.** ## Checklist 1. **Config file:** write `.conductor/settings.toml` — shared/committed. **Only takes effect in workspaces created AFTER it merges to the default branch** (see the warning below). 2. **Discover repo conventions — never invent commands.** Read `package.json` `scripts`, `Makefile`/`justfile`/`Taskfile`, README, Procfile, compose files, `.env*.example`, and any existing `.conductor/settings.toml` / legacy `conductor.json`: ```bash jq '.scripts' package.json 2>/dev/null grep -E '^[a-zA-Z_-]+:' Makefile justfile Taskfile* 2>/dev/null cat .conductor/settings.toml 2>/dev/null ``` 3. **Configure setup and archive automatically** — don't ask whether to include them. Then work through **run** below. ### Setup (automatic) Runs once after workspace creation, from the workspace directory. Use it for installs, `.env` copies from `$CONDUCTOR_ROOT_PATH`, symlinks, submodules. Pick the command from discovered conventions