complexity-review

Review architectural proposals against 30 complexity dimensions for simpler alternatives.

19|1|Updated Jan 10, 2026

Search Tags:#architecture #complexity #review #risk-management #simplification #decision-making

Ready to run

npx skills add https://github.com/eferro/augmented-lean-delivery --skill complexity-review-eferro

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: complexity-review
Source: https://github.com/eferro/augmented-lean-delivery/tree/main/complexity-review
Command: npx skills add https://github.com/eferro/augmented-lean-delivery --skill complexity-review-eferro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews technical proposals and architectural decisions against 30 complexity dimensions, pushing teams toward the simplest viable and safest options.

Core Features & Use Cases

Systematically reviews proposals against the 30 complexity dimensions
Proposes simpler alternatives and identifies postponement opportunities
Applies to architectural decisions, technology selections, and system redesigns
Helps answer questions like when to avoid microservices, event sourcing, or Kafka in favor of simpler solutions

Quick Start

Submit a technical proposal and request a complexity review.

Frequently Asked Questions about complexity-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I review my architecture proposal for unnecessary complexity?▼

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.

When should I avoid microservices or event sourcing in favor of simpler solutions?▼

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.

What do I need to provide to get a complexity review of my system design?▼

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.

Can this review help with technology selection and system redesigns?▼

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.

Does the complexity review work for architectural decisions without explicit constraints?▼

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.

What is the best way to simplify architectural decisions safely?▼

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.