reduce-complexity

/cl-dev:reduce-complexity runs an interactive review that hunts for unnecessary complexity and pushes toward a simpler shape.

What it does

It works through your material with you: a solution design, an implementation plan, or existing code. It points out the spots that are harder to understand or change than they need to be. For each one, it explains why it's a problem in plain terms and works with you to find a cleaner alternative, so you leave with concrete, simpler options rather than a vague sense that "this feels heavy."

It's a conversation. You're in the loop, weighing the trade-offs and deciding what to change.

When to use it

Reach for it whenever something feels over-engineered, or before you commit to a shape you'll have to live with. It fits most naturally right after /cl-dev:design-solution, while the approach is still cheap to change. Catching complexity on paper is far cheaper than unwinding it from shipped code. It pairs with /cl-dev:review-design: that review checks structure, security, and privacy, while this one focuses squarely on simplicity.

It also works well on an implementation plan before you build, or on code you've already written when a change turned out messier than expected. Use it any time you want a second opinion on whether there's a simpler way.

How to invoke it

Run it in your coding agent:

/cl-dev:reduce-complexity

Point it at whatever you want reviewed: a design or plan for the current work item, or a specific area of code. If you're partway through the workflow, it picks up the design or plan you're working on; otherwise, tell it what to look at when you invoke it.