openspec-repairlisted

Turns a classified gap — from openspec-verify, openspec-drift, or an executor's deviation tag — into a concrete, routed fix plan. Decides which of the four repair routes a gap takes (fix the code, update the spec, open a new change, or block), and never resolves a gap by weakening what was agreed.
mshegolev/gsd-openspec-integration · ★ 0 · AI & Automation · score 73

Install: claude install-skill mshegolev/gsd-openspec-integration

## Purpose A gap with no owner and no route is just a warning people learn to scroll past. This skill exists so every finding produced anywhere in the integration terminates in exactly one of four named actions, with the "make the audit pass by lowering the bar" option structurally unavailable. ## Invocation conditions - Composed by `openspec-audit` whenever a composed skill reports a finding requiring a fix. - After `openspec-verify` writes `status: gaps_found` — this is the natural next step before re-running verification. - Directly, `/openspec-repair [finding-id]`, to plan the fix for one specific gap. ## Required inputs - One or more findings, each already carrying a classification. This skill classifies nothing itself — classification is `openspec-execute`'s (execution-time deviations) and `openspec-drift`'s (audit-time drift classes). An unclassified input is rejected, not guessed at. - `.planning/openspec/TRACEABILITY.md` for the affected requirement's current resolution. ## Files read - `.planning/openspec/DRIFT.md`, `AUDIT-SUMMARY.md` - `.planning/phases/<NN>-<slug>/<NN>-OPENSPEC-VERIFICATION.md`, `SUMMARY.md` - `openspec/changes/<change_id>/{proposal,design,tasks}.md` and `specs/**/spec.md` ## Files this skill may write - `.planning/openspec/REPAIR-PLAN.md` (overwritten per run) - Never writes to `openspec/` — spec changes go through `/opsx:update`, which is OpenSpec's own authoring path, so the spec's own validation and authorship conventions apply. - Nev