speckit-ripple-check

What problem does it solve?

This Skill solves the problem of verification drift after you fix issues found by a previous ripple scan, ensuring that each previously OPEN finding still applies and that your changes did not introduce new side effects.

Core Features & Use Cases

• Re-checks existing OPEN findings: Reloads ripple-report.md and re-evaluates each finding’s status by reading the current code at the referenced file/line.
• Detects resolution quality: Produces RESOLVED, MITIGATED, OPEN, WORSENED, or STALE outcomes based on whether the side effect still exists, was reduced, worsened, or became unavailable due to refactoring.
• Scans for fix-induced side effects: If a finding changes status, analyzes the changed lines to discover newly introduced ripple effects and appends them as new findings.
• Updates audit-ready artifacts: Modifies ripple-report.md in place, recalculates counts, updates the Coverage Gap Matrix, and appends a deduplicated Check History row.

Quick Start

Run /speckit.ripple.check critical to re-verify only the currently CRITICAL OPEN findings and update ripple-report.md accordingly.