Stats

Actions

Tags

Help us improve

Share bugs, ideas, or general feedback.

architecture-review-checklist | architecture-governance | ClaudePluginHub

Skill

architecture-review-checklist

From architecture-governance

Standardized architecture review process with consistent criteria. Evaluate systems against principles, quality attributes, and operational readiness. Use when conducting architecture reviews.

$

npx claudepluginhub sethdford/claude-skills --plugin architect-governance

Popularity

Parent stars

13

Parent forks

2

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/architecture-governance:architecture-review-checklist

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Establish standardized architecture review process with clear criteria and repeatable outcomes.

SKILL.md

54 lines · ~798 tokens

Similar Skills

well-architected

19

Guides architecture reviews using a 6-pillar framework (operational excellence, security, reliability, performance, cost, sustainability) for ARCH documents. Forces explicit answers before shipping.

4 tools

architecture-reviewer

236

Delivers systematic architecture reviews across 7 dimensions with scored reports, highlighting risks and recommendations.

14 files

architecture-review

13

Deep architectural review of a platform or product — cross-references code against claims, maps failure modes, evaluates scaling bottlenecks, and produces a decision-grade handoff document with ADRs. Use when: reviewing an existing system for scaling readiness, performing a CTO handoff, evaluating platform architecture for enterprise readiness, or auditing a codebase before a major migration. Triggers: architecture review, scaling review, platform review, CTO handoff, system audit, scaling analysis, architecture assessment, production readiness.

10 tools

Stats

Parent stars13

Parent forks2

MaintenanceFair

Last CommitMar 11, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Architecture Review Checklist

Establish standardized architecture review process with clear criteria and repeatable outcomes.

Context

You are conducting architecture reviews. Evaluate designs against principles, quality attributes, operational readiness. Use consistent checklist; document decisions and rationale.

Domain Context

Based on architecture review frameworks and governance:

Design Review: Does proposed design align with principles? Are quality attributes met? Trade-offs understood?
Operational Readiness: Monitoring, alerting, logging, runbooks documented? Disaster recovery plan? Capacity forecast?
Security Review: Authentication, authorization, secrets management, data protection? Compliance with regulations?
Cost Impact: Infrastructure cost projections? Optimizations considered? Budget alignment?

Instructions

Prepare Checklist:
- Alignment: Does design follow architecture principles?
- Quality Attributes: Addresses scalability, reliability, security, maintainability?
- Dependencies: External services, databases, message queues? All documented?
- Operations: Monitoring, alerting, logging, runbooks? On-call procedure?
- Testing: Unit tests, integration tests, chaos testing? Coverage adequate?
- Compliance: GDPR, CCPA, HIPAA? Data residency requirements met?
- Cost: Projected monthly cost? Optimization opportunities?
Conduct Review: Present architecture. Walk through checklist. Score each item: met, partially met, not met. Discuss gaps and remediation.
Document Decision: Record what's approved, what needs work, contingencies. Link to design document. Assign owners for open items.
Track Follow-Up: Monitor that remediation happens before deployment. Close items only after verification.
Iterate: If review uncovers major issues, schedule follow-up review. Use past reviews to improve checklist.

Anti-Patterns

Reviews Without Teeth: Checklist completed, issues noted, nothing changes. Result: wastes time. Guard: Reviews block deployment; open items must be resolved or documented as accepted risk.
Checklist Without Context: Rote questions without understanding trade-offs. Result: surface-level feedback. Guard: Reviewer understands domain; asks "why?" on answers.
No Documentation: Verbal feedback, forgotten after meeting. Result: team doesn't know what was approved. Guard: Written decision with rationale; link to design docs.
Infrequent Reviews: Only at major milestones. Result: missed issues accumulate. Guard: Reviews on feature gates, before production, monthly architecture sync.

Further Reading

Software Architecture in Practice by Len Bass et al. — architecture review processes
Architectural Thinking by Nathaniel Schutta — critical evaluation skills
Software Architecture Fundamentals by Mark Richards — review and governance