What problem does it solve? Deciding the shape of a solution is cheapest before any plan exists, yet a single agent writing a plan cannot credibly contest the shape it is about to detail. This Skill explores three competing solution designs for a feature request or bug report as isolated staff-level Engineering Leads, then has a skeptical judge select one on the record. ## Core Features & Use Cases - Three Isolated Authors: Fans out three sub-agents optimizing for minimum change, cleanest architecture, and unconstrained reframing, each writing its own approach file without seeing the others. - Skeptical Judge: A fourth sub-agent attacks the self-reported claims in all three approaches and selects exactly one, with comparative justification and non-binding carry-overs. - Slot-Based Workflow: Accepts a full path to a featurerequest.md or bugreport.md, or a slot number that expands to scratch/[MMDD]-[##]/, and supports regenerate, refine, and judge-only re-invocation modes. - Use Case: Before planning a new FHIR cross-version mapping feature, run this Skill on the captured feature request to get three competing designs and a written verdict that dev-plan can build from. ## Quick Start Run the dev-approach skill on slot 2 to generate three competing solution approaches and a judged selection for the feature request captured there.
