complexity-review

Review architecture proposals by submitting a concrete technical design with explicit constraints for a complexity review. The Skill evaluates the proposal against 30 complexity dimensions to identify unnecessary additions and propose safer, simpler alternatives.

Avoid microservices or event sourcing when a complexity review identifies simpler viable configurations. The Skill challenges technology selections by requiring data-driven checks to justify added complexity and suggesting postponement where possible.

Provide a concrete technical proposal and explicit constraints to receive a complexity review. The Skill requires these inputs to evaluate your system redesign against 30 dimensions and guide your team toward minimal viable configurations.

Yes, technology selection and system redesigns are core use cases for this complexity review. It systematically evaluates proposed architectures to identify postponement opportunities and push teams toward the simplest viable and safest options.

No, a complexity review requires explicit constraints and a concrete proposal to function. Without these inputs, the Skill cannot perform data-driven checks to justify added architectural complexity or propose simpler alternatives.

Simplify architectural decisions safely by applying a complexity review across 30 dimensions. This process systematically identifies unnecessary complexity, proposes minimal viable configurations, and postpones risky additions until justified by data-driven checks.