review-risk

Analyze distributed system design documents for resilience and Saga consistency risks.

12|1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/wfukatsu/nexus-architect --skill review-risk-wfukatsu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-risk
Source: https://github.com/wfukatsu/nexus-architect/tree/main/skills/review-risk
Command: npx skills add https://github.com/wfukatsu/nexus-architect --skill review-risk-wfukatsu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill identifies potential risks in distributed system designs, analyzing failure modes and ensuring Saga design adequacy.

Core Features & Use Cases

  • Distributed System Risk Analysis: Evaluates network partitions, clock skew, split-brain scenarios, and cascading failure paths.
  • Failure Mode Analysis: Inspects behavior during service call timeouts, circuit breaker patterns, bulkhead isolation, and graceful degradation.
  • Saga Design Adequacy: Reviews compensating transactions, orchestration/choreography choice, handling of partial failures, and idempotency guarantees.
  • Data Consistency Risks: Assesses eventual consistency windows, read-your-write guarantees, and conflict resolution strategies.

Quick Start

Review risks in your distributed system by executing the review-risk skill with the design documents as input.

Frequently Asked Questions about review-risk

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

FAQPage Schema
How do I analyze risks in distributed system design documentation?

To analyze distributed system design risks, you can execute a review process that evaluates network resilience, fault tolerance, and Saga consistency by passing your system design documentation as input for parallel analysis.

What is Saga design adequacy and how is it reviewed?

Saga design adequacy reviews compensating transactions, orchestration versus choreography choices, partial failure handling, and idempotency guarantees within distributed systems to ensure transactional consistency across services.

How do I assess data consistency risks in distributed systems?

Assessing data consistency risks involves evaluating eventual consistency windows, read-your-write guarantees, and conflict resolution strategies to maintain data integrity across distributed services.

What distributed system risks should I check before deployment?

Before deployment, check distributed system risks including network partitions, clock skew, split-brain scenarios, and cascading failure paths to ensure network resilience and fault tolerance.

Can I use system design documents to check for network partition risks?

Yes, you can use system design documents to check for network partition risks by executing a risk analysis that evaluates network resilience, split-brain scenarios, and cascading failure paths.