state-consistency-investigator

Compare source-of-truth data, replicas, and caches to diagnose state divergence and lag.

8|1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/bordenet/superpowers-plus --skill state-consistency-investigator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: state-consistency-investigator
Source: https://github.com/bordenet/superpowers-plus/tree/main/skills/engineering/state-consistency-investigator
Command: npx skills add https://github.com/bordenet/superpowers-plus --skill state-consistency-investigator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses cross-service state inconsistencies across distributed systems by pinpointing replication lag, cache staleness, and event-ordering issues that degrade data integrity.

Core Features & Use Cases

  • Cross-source consistency analysis across primary databases, replicas, and caches to surface divergences and lag.
  • Evidence-driven investigation protocol: replication lag measurement, event order checks, and cache invalidation tracing.
  • Useful when debugging data inconsistency incidents such as stale reads, out-of-order events, or cross-service divergence.

Quick Start

Describe the incident, specify affected entities, and request a cross-source evidence report detailing replication lag, event ordering, and cache invalidation findings.

Frequently Asked Questions about state-consistency-investigator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose state inconsistencies across distributed services?

Diagnose state inconsistencies by comparing source-of-truth data, replicas, and caches to identify divergence, which outputs a structured evidence report detailing replication lag and cache invalidation issues.

What causes stale reads and out-of-order events in microservices?

Stale reads and out-of-order events in microservices are typically caused by replication lag, cache staleness, and event-ordering issues during asynchronous data propagation across distributed services.

How do I trace cache invalidation races during a data integrity incident?

Trace cache invalidation races by applying an evidence-driven investigation protocol that performs cross-source consistency analysis across primary databases and caches to surface divergences.

Can I measure replication lag between primary databases and read replicas?

Yes, you can measure replication lag by executing cross-source consistency analysis across primary databases and replicas, assessing data propagation delays to pinpoint divergence and asynchronous update issues.

What is the best way to document cross-service divergence during an incident?

Document cross-service divergence by generating a structured evidence report that details replication lag measurements, event ordering audit findings, and cache behavior analysis for the affected entities.

Is this approach suitable for debugging asynchronous data propagation in microservices?

Yes, this approach is designed for debugging asynchronous data propagation in microservices, specifically targeting incidents involving delayed updates, cache invalidation races, and event-ordering issues across distributed environments.