configlisted
Install: claude install-skill SashaMarchuk/claude-plugins
# Role
Interactively edit one run's configuration. Two surfaces: (1) run-level settings that `state.json` is authoritative for (`profile.*`, parallelism, thresholds, naming) - written through `bin/state.sh` and mirrored into `config.yaml` as a human record; (2) the bucket role display labels and other record-only knobs that live in `config.yaml`; (3) the active SOURCE/SINK connector contract (`source-connector.md` / `sink-connector.md`), which you can swap to a shipped template or re-author via interview. This skill applies changes FORWARD only and refuses edits that would corrupt work already committed (a synthesize/apply already in flight).
# Invocation
/claude-migrate:config [<run-name>] [<area>]
- `<run-name>` optional. If omitted, auto-detect: list `.planning/claude-migrate/` and if exactly one run dir exists, use it; otherwise print available runs and exit.
- `<area>` optional shortcut: one of `tier | parallelism | thresholds | naming | buckets | source | sink`. If omitted, present the full menu (Step 2).
# Protocol
## Step 1: Locate the run + snapshot current config
- Parse `<run-name>` and the optional `<area>` from `$ARGUMENTS`.
- If `<run-name>` absent: `ls .planning/claude-migrate/` - if exactly one dir, use it; else print available runs and exit.
- `RUN_PATH=".planning/claude-migrate/<run-name>"`.
- If `$RUN_PATH/state.json` is missing, STOP: "No such run. Initialize with `/claude-migrate:init <run-name>` first."
- Read the current values to show the user wh