cross-module-consistency-auditor

What problem does it solve?

It prevents production defects where a single change is correctly applied in one place but missed or inconsistently implemented across modules, flows, reports, APIs, and copied logic.

Core Features & Use Cases

• Impact Map generation: Identify the change kernel and map the full blast radius across input, persistence, aggregation, display, API/export, reverse flows, permissions, and downstream jobs.
• Cross-Module Consistency Matrix: Convert consistency rules into a rules-vs-modules checklist with PASS/FAIL/NOT TESTED/N/A outcomes and owners for action items.
• Copy Propagation Review Strategy: Select a canonical implementation and apply diff-based reviews to copied instances to avoid redundant effort while still catching divergence.
• Test Checklist conversion: Turn consistency rules into testable assertions (totals reconciliation, sign inversion, report vs drill-down matching, state transition checks).
• Open-questions capture: Record uncertain modules as [NEEDS CONFIRMATION] and track missing touchpoints that must be resolved.

Quick Start

Ask the skill to audit a specification change by providing the change description, the candidate source-of-truth location, and a list of affected modules/flows/reports/APIs so it can produce an impact map and a consistency matrix.