Uno-Reverse: Radical Simplification & Red-Teaming

"Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." — Antoine de Saint-Exupéry

The uno-reverse skill provides a rigorous contrarian simplification and red-teaming framework. While standard engineering processes naturally drift toward feature accretion, defensive layering, and speculative generalization, uno-reverse forces the opposite trajectory: aggressive subtraction, primitive collapsing, and minimum viable execution.

🎭 Impartial Review: Dedicated Subagent Delegation (Default)

To guarantee the integrity and rigor of an Occam's Razor red-team assessment, uno-reverse reviews must be conducted by a dedicated, isolated subagent rather than within the invoking agent's active conversation context.

1. Rationale: Why In-Context Audits Fail

When an agent that designed, brainstormed, or iteratively implemented a solution attempts to evaluate its own work inline, the review suffers from three critical failure modes:

1. Confirmation Bias & Sunk-Cost Defense: An agent that spent multiple conversation turns proposing abstractions, schemas, microservices, or config flags naturally rationalizes their existence. A dedicated subagent has zero psychological or conversational investment in prior proposals.
2. Context Contamination: Long-running conversation contexts contain discarded ideas, exploratory reasoning, edge-case anxieties, and premature compromises. This cognitive residue biases the evaluation toward maintaining accidental complexity. A fresh subagent receives only the target specification and the audit mandate, evaluating it with a clean slate.
3. Preserving Impartiality & Objective Distance: Genuine red-teaming requires contrarian detachment. An isolated subagent is uninhibited by politeness or conversational continuity—it can objectively propose deleting 90% of a specification without defending earlier dialogue.