analyzing-system-design

To analyze system design for atomicity and consistency, run a seven-lens assessment covering idempotency, concurrency, resilience, architectural patterns, and CAP considerations. This process surfaces reliability risks and outputs a structured system-design-analysis.md artifact to guide implementation.

A seven-lens system design analysis evaluates distributed systems through atomicity, idempotency, consistency, concurrency, resilience, architectural patterns, and CAP considerations. It assesses correctness and reliability for cross-service changes before implementation begins.

Perform architecture analysis after research and before coding during feature development. Assessing data integrity, concurrency, and CAP considerations early ensures scalable design and produces a written system-design-analysis.md artifact to guide engineers and stakeholders.

Document system design trade-offs by generating a system-design-analysis.md artifact that records approved decisions and proposes actionable improvements. Include Mermaid diagrams when applicable to visually communicate architectural patterns and resilience strategies to stakeholders.

Yes, this system design analysis supports complex cross-service changes by evaluating concurrency, consistency, and CAP considerations across distributed systems. It assesses architectural patterns and resilience to ensure data integrity and correctness for standard and complex tasks.

Automated architecture analysis requires an existing implementation plan and research context to function. It surfaces design risks and proposes trade-offs, but developers must review the generated system-design-analysis.md and explicitly approve decisions before proceeding to coding.