What problem does it solve? Design decisions made from a single framing often fail: a component that looks right in isolation clashes with the system around it, or a plan loyal to the big picture ignores what the part actually needs. This Skill resolves one design question twice — once component-first, once system-first — then names every divergence so scope mismatches and sizing errors surface before requirements freeze or an approach locks. ## Core Features & Use Cases - Three-pass scope sweep: Resolves the same question at close-up (part-first), pulled-back (whole-first), and synthesis zoom levels, producing a gap read no single framing yields. - Structured tension report: Outputs enumerated divergences, a resolution sketch per divergence, design tensions, criteria implications, and an ALIGNED or DIVERGENT coherence verdict. - Use Case: Before building a retry wrapper around a flaky vendor API, run the sweep to discover the platform already has a shared queue with dead-letter handling — the gap read recommends expressing backoff as queue options instead of a parallel delivery system. ## Quick Start Use aperture oscillation on this design decision: the build target is X and the surrounding intent is Y — give me the close-up view, the system view, and the gap read.
