design-challenger

To simplify an overcomplicated system design, you identify unnecessary indirections and bulky workflows, then consolidate responsibilities into structured alternatives with explicit trade-offs documented for each option.

The best way to evaluate architecture trade-offs is to compare cleaner design alternatives that reduce moving parts, documenting the specific compromises and structural benefits of each proposed system design.

You identify drivers of overcomplication by analyzing high-level designs for fragmented invariants, unnecessary handoffs, and bulky workflows, mapping how these elements complicate system reasoning and maintenance.

Yes, you can propose structured design alternatives without altering the code structure by focusing purely on high-level architecture evaluation, producing actionable design proposals and explicit trade-offs for review.

You should not use design simplification when your system relies on necessary indirections for strict protocol compliance or security boundaries, as consolidating these moving parts may break critical invariants.

Design-challenger requires referencing project context because protocol simplification tasks need accurate awareness of existing system invariants and handoffs to propose executable, structured alternatives with explicit trade-offs.