What problem does it solve? Deciding a solution's shape is cheapest before any plan exists, yet a single agent planning its own design cannot credibly challenge it. This Skill explores three competing solution shapes for one request as isolated staff-level Engineering Leads, then has a skeptical judge sub-agent select one on the record. ## Core Features & Use Cases - Three isolated authors: Author A optimizes for minimum change, Author B for cleanest architecture, and Author C for an unconstrained shape, each writing its own approach file without seeing the others. - Skeptical judge: A separate sub-agent attacks the self-reported claims in all three approaches and selects exactly one, with comparative justification and non-binding carry-overs. - Flexible input and re-invocation: Accepts a full path to a featurerequest.md or bugreport.md, or a slot number expanding to scratch/[MMDD]-[##]/, and supports regenerate, refine, and judge-only modes on re-runs. - Use Case: Before planning a new caching feature, run this Skill on the feature request to get three competing designs and a recorded judgment, then hand the selection to dev-plan. ## Quick Start Run dev-approach on slot 2 to generate three competing solution approaches and a judged selection from the feature request in today's scratch directory.
