implementation-harness-evaluate-fitlisted

Use when the user wants to check whether an already-installed harness is well-tuned to THIS project and fix any mismatches — phrases like "evaluate the harness fit", "does the harness suit this project", "check in on the harness", "tune the harness to the project", "the facets/floor look wrong for this repo", "/evaluate-fit". Runs a full multi-agent DEEP DIVE of the project (stack, module structure, risk profile, deploy/notify story, secret + visual surfaces), reads the CURRENT harness config, then produces ranked, evidence-backed recommendations across the ONLY customizable surfaces — the `custom/` overlay, `harness.env` knobs, and `facets.json` (`layer` vocabulary + `policy`) — and, on your approval, applies them. It NEVER edits harness mechanism (scripts/docs/dashboard) — an install stays fork-free and upgrade-clean. Ideal after a harness was scaffolded against an empty/young repo, or after the project has grown. Requires a scaffolded `.harness/`.
RyanMKrol/claude-skills · ★ 0 · AI & Automation · score 73

Install: claude install-skill RyanMKrol/claude-skills

# Evaluate harness fit — tune the customizable surface to THIS project The `implementation-harness:implementation-harness-create` step scaffolds a *generic* harness and tailors what it can from whatever the project looked like at setup — which is often **almost nothing** (a fresh repo). As a project takes shape, the harness's project-specific knobs (the difficulty **floor**, the `layer` facet vocabulary, the `custom/` overlay) can drift out of fit, and there is otherwise **no path to re-fit them** except the slow runtime poor-fit gate. This skill closes that gap: it studies the project in depth, diffs that understanding against the harness's *customizable* surface, and applies the fixes you approve. `customize` is the reactive menu ("here are the features, which do you want?"). **This skill is the proactive diagnostician** ("here is what YOUR project needs and why"). It reuses `customize`'s overlay mechanics and delegates the tier ladder to `update-ladder`; it does not duplicate them. Read this whole file, then execute in order. ## 0. Pre-flight - Require a harness: `.harness/scripts/loop.sh`, `.harness/config/harness.env`, and `.harness/config/facets.json` must exist. If not, send the user to `implementation-harness:implementation-harness-create` and stop. - Read the installed version for context: `cat .harness/.harness-version 2>/dev/null`. - Note `$ARGUMENTS`: if it names a focus area (e.g. `facets`, `hooks`, `floor`, `visual`), you may still run the full dive but