Conducts comprehensive architecture design reviews including system design validation, architecture pattern assessment, quality attributes evaluation, technology stack review, and scalability analysis. Produces detailed review reports with findings, recommendations, and risk assessments. Use when reviewing software architecture designs, validating architecture decisions, assessing system scalability, evaluating technology choices, or when users mention architecture review, design assessment, technical review, or architecture validation. Use when this capability is needed.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Conducts comprehensive architecture design reviews including system design validation, architecture pattern assessment, quality attributes evaluation, technology stack review, and scalability analysis. Produces detailed review reports with findings, recommendations, and risk assessments. Use when reviewing software architecture designs, validating architecture decisions, assessing system scalability, evaluating technology choices, or when users mention architecture review, design assessment, technical review, or architecture validation. Use when this capability is needed.
metadata
{"author":"dauquangthanh"}
Architecture Design Review
Conduct systematic architecture design reviews to validate system design, assess quality attributes, evaluate technology choices, and identify risks before implementation.
Review Process
Follow this structured approach for comprehensive architecture reviews:
Note: For technology selection guidance (frameworks, databases, cloud platforms), reference the architecture-design skill.
Critical Review Principles
Focus on Architecture, Not Implementation:
Review designs and patterns, not code quality
Validate decisions and trade-offs, not syntax
Assess structure and boundaries, not variable names
Be Specific with Findings:
✅ "Circuit breaker missing on Order→Payment calls (avg 50 calls/sec). Add Resilience4j with 50% error threshold."
❌ "Need better error handling"
Quantify Performance Requirements:
✅ "API response time must be <200ms for 95th percentile at 1000 req/s"
❌ "API should be fast"
Provide Actionable Recommendations:
✅ "Split UserService into Authentication (identity) and Profile (data) services. Estimated 3-week effort. Use event bus for sync."
❌ "Consider improving service boundaries"
Assess Based on Context:
Startup MVP has different requirements than enterprise system
100-user system doesn't need microservices complexity
Evaluate appropriateness for scale, team, and timeline
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
