architecture-review

To review architecture documentation for scalability risks, provide your docs/architecture.md file to receive a structured critique identifying gaps, security considerations, dependency management issues, and explicit fixes for each problem.

The best way to identify potential improvements is through a structured evaluation that checks architecture documents for incremental deployability, security, and dependencies, outputting actionable recommendations and a readiness rating with rationale.

Yes, an architecture review applies structured critique to typical scenarios such as incremental deployability and dependency management, identifying specific risks and proposing concrete fixes to improve system readiness.

Yes, you can receive explicit fixes for each identified issue and a readiness rating with rationale by submitting your architecture documentation for a structured review against completeness, security, and dependency criteria.

You need a structured critique when architecture decisions diverge across teams or as projects scale, requiring a review of docs/architecture.md to uncover hidden gaps, risks, and improvement opportunities before deployment.

A limitation of reviewing architecture documentation is that it relies on the completeness of docs such as architecture.md and idea.md, meaning undocumented design decisions or implicit dependencies may not be captured in the readiness rating.