just enough

Technical teams often fall into the trap of over-engineering, building for future-proof scenarios that never arrive or adding layers to manage problems caused by previous complexity. This skill acts as a critical reasoning lens to identify unjustified complexity and restore focus on the actual goal. It treats complexity as a cost that must earn its place through measurable value, risk reduction, or necessity.

What it does

• Outcome mapping identifies the core objective to separate essential requirements from assumed ones.
• Cost-value audit weighs direct, indirect, and opportunity costs against the value a specific feature or process provides.
• Dependency analysis flags "complexity loops" where new systems exist solely to manage the overhead of previous ones.
• Simpler-path benchmarking generates a plausible, minimal alternative to serve as a baseline for comparison.
• Counterfactual testing uses zero-based reasoning to determine if a component would be included if starting from scratch today.

How it works

1. Invoke the lens when a plan, system architecture, or decision feels bloated or over-engineered.
2. Deconstruct the current approach by listing the components and their intended purpose or risk mitigation.
3. Run the reassessment to surface where complexity is unjustified by present-day evidence.
4. Compare and recommend by contrasting the current state against a simpler alternative and highlighting what can be removed or deferred.

Frameworks & tools

This skill is platform-agnostic and works across software architecture, project management frameworks, product roadmaps, and organizational processes.

Why this beats prompting it yourself

Standard prompts often default to "make this simpler," which can lead to losing critical safeguards or context. This skill uses a sophisticated trade-off model that preserves justified complexity—like security, regulatory needs, or safety—while ruthlessly questioning everything else.

Use cases

• Architecture reviews to prevent over-engineering in microservices or database schemas.
• Product roadmapping to prune features that don't solve the core user pain point.
• Process refinement to eliminate bureaucratic steps that no longer serve their original purpose.
• Refactoring decisions to determine if a complex rewrite is worth the opportunity cost.

Known limitations

Does not automate technical implementation. Requires the user to provide the context of the goal and current constraints. Does not replace domain-specific safety or legal audits.