implementation-harness-update-ladderlisted

Use when the user wants to add, swap, or remove a rung on this project's difficulty/tier ladder — phrases like "add a model to the ladder", "update the tier ladder", "add haiku to the ladder", "change the escalation ladder", "/update-ladder". Interviews for which model and whether it's a SWAP (replace a model at a fixed position) or an INSERT/REMOVE (changes rung count, shifts positions), handles models with no effort parameter (e.g. Haiku) via `effort: null`, and walks the correct migration path for each — the "Bumping the base model" runbook for a swap, or a no-ledger-migration note for an insert/remove (plus a reminder to raise `exploreProbabilityPM` so a newly inserted rung doesn't sit inert on already-calibrated work, and `exploreCooldownN` so a rejected rung eventually gets rechecked instead of staying excluded forever). Requires the harness scaffolded, and harness version >= 1.45.0 for the effort-less-rung path / >= 1.47.0 for downward exploration / >= 1.48.0 for the recheck cooldown (older installs do
RyanMKrol/claude-skills · ★ 0 · AI & Automation · score 73

Install: claude install-skill RyanMKrol/claude-skills

# Update the tier ladder You walk the user through changing `.harness/config/facets.json → .tiers.ladder` — the global difficulty escalation ladder (`.harness/docs/designs/difficulty-autotune.md`) — for THIS project. Focus target: `$ARGUMENTS` (a model id, if given, skips straight to asking what to do with it). Read this whole file, then execute in order. ## 0. Pre-flight - Confirm `.harness/docs/HARNESS.md` and `.harness/config/facets.json` exist — if not, this project isn't scaffolded; point the user at `implementation-harness:implementation-harness-create` and stop. - Read the current `.tiers.ladder` from `.harness/config/facets.json` and show it to the user as the starting point. - Read `.harness/.harness-version`. **Effort-less rungs (`effort: null`) need >= 1.45.0.** If the installed version is older and the user's change would introduce a null-effort rung, tell them plainly and offer, via `AskUserQuestion`, to run `implementation-harness:implementation-harness-upgrade` first — don't hand-write the mechanism support yourself; that's exactly the kind of local fork this harness avoids (see the project's own `CLAUDE.md`). ## 1. What's changing Ask (`AskUserQuestion`) which model to add/change, and whether it's a: - **Swap** — replace the model at an existing rung, same position, same rung count. - **Insert** — add a brand-new rung (e.g. a cheaper tier-0, or a rung between two existing ones), changing the rung count and shifting later positions. - **Remov