design-reviewer

Review architecture and system design documents for design flaws with severity ratings.

Updated Mar 10, 2026
One-click install
npx skills add https://github.com/Haaaiawd/SparkMate --skill design-reviewer-haaaiawd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-reviewer
Source: https://github.com/Haaaiawd/SparkMate/tree/main/.agent/skills/design-reviewer
Command: npx skills add https://github.com/Haaaiawd/SparkMate --skill design-reviewer-haaaiawd

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the critical need for thorough and systematic review of architecture and system design documents, preventing costly errors and ensuring robustness before implementation.

Core Features & Use Cases

  • Systematic Design Review: Utilizes a three-dimensional framework (System Design, Runtime Simulation, Engineering Implementation) to identify potential flaws.
  • Risk Identification & Prioritization: Uncovers design defects, inconsistencies, and potential failure points, categorizing them by severity (Critical, High, Medium, Low).
  • Use Case: A team is about to finalize the architecture for a new microservices platform. They use this Skill to review the architecture overview, system design documents, and ADRs to catch potential issues like circular dependencies, race conditions, or unaddressed edge cases before development begins.

Quick Start

Use the design-reviewer skill to review the architecture documents and identify any critical design flaws.

Frequently Asked Questions about design-reviewer

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

FAQPage Schema
How do I systematically review architecture designs for potential flaws?

Systematically review architecture designs using a three-dimensional framework covering system design, runtime simulation, and engineering implementation to identify and prioritize flaws by severity before implementation begins.

What is a pre-mortem analysis for system design documents?

Pre-mortem risk assessment for system design documents analyzes dependencies, state management, concurrency, and testability to uncover potential failure points and categorize design defects by severity.

How do I identify circular dependencies and race conditions in my architecture overview?

Identify circular dependencies and race conditions in architecture overviews by simulating runtime behavior and analyzing engineering implementation constraints to ensure architectural consistency and runtime robustness.

Can I use this framework to review microservices architecture and ADRs?

You can review microservices platform architecture and ADRs using this framework to catch unaddressed edge cases, assess engineering feasibility, and ensure architectural consistency across distributed components.

What's the best way to assess engineering feasibility and testability in system design?

Assess engineering feasibility and testability in system design by applying a structured review framework that analyzes implementation constraints, security boundaries, and state management to prioritize identified design flaws.

When should I not use an automated design review for architecture documents?

Automated design review for architecture documents should not replace manual peer review when evaluating nuanced domain logic, but it is highly effective for identifying structural inconsistencies and unaddressed edge cases.