What problem does it solve?
When a fix starts feeling like a band-aid, this Skill forces a structured comparison between the current abstraction and a clean-slate redesign, so you stop layering wrappers on a broken shape and decide deliberately whether to refactor locally or redesign the surface.
Core Features & Use Cases
- Structured Decision Ritual: A six-part template (current path, friction, radical option, deletion prize, user loss, decision) that makes redesign trade-offs explicit before any code changes.
- Mental Inlining Pass: Systematically evaluates whether helpers, wrappers, and adapters earn their existence by owning invariants, isolating unsafe input, or simplifying multiple callers.
- Asymmetric Option Check: Identifies single refusals that delete entire code families such as adapters, flags, defensive checks, and migration branches.
- Use Case: You are about to add a third boolean flag to track workspace teardown state. The Skill prompts you to go up one level, redesign teardown as a single owning transition, and delete all downstream readiness checks.
Quick Start
Before making this edit, run the radical options ritual to compare the current abstraction against a from-scratch design and tell me which to take.
