Architecture Review
- Establish constraints and assumptions first.
- Evaluate coupling, cohesion, failure modes, observability, and operational complexity.
- Prefer incremental improvements over rewrites when practical.
- State trade-offs explicitly.
Use when the user explicitly asks to review or evaluate system architecture, service boundaries, scalability, distributed-system design, or architectural trade-offs.
npx skillmds@latest add rhenter/architecture-review rhenter/agent-skills/tree/main/skills/architecture-review commit 3c5fd17a35