specflow-brainstormlisted

# Specflow: Brainstorm ## When to use Turn a half-formed idea into an agreed design that lands as a spec. The front of the spec-first spine (brainstorm → plan → develop). Assesses scope and decomposes an over-large ask, asks ONE question at a time, surfaces the specs, decisions, and rules the idea already touches, then proposes two or three real approaches with a recommendation — and writes no implementation code until the developer agrees and the spec exists. Use when the user says "let's build X", "I want to add", "what if we", "how should we approach", "I'm thinking about", or brings any idea that is not yet a spec. In a Specflow project this runs before specflow-plan and specflow-develop. ## The Iron Law NO IMPLEMENTATION BEFORE AN AGREED DESIGN AND A SPEC Violating the letter of this law is violating the spirit. If you find yourself constructing a reading under which this idea does not need agreeing first, that construction is the violation. Hardening mechanisms per `skills/_conventions/hardening.md`. ## What this produces An **agreed design that becomes a spec**. Not a design document, not a dated write-up under `docs/` — a dev spec under `.specflow/specs/` and, if the outcome was never articulated, the business spec it `implements:`. In this profile, specs are where agreements live; a second place to record designs is how the two trees drift. The narrative of *why* this approach beat the alternatives may also land in `.cortex/atlas/decisions/` — that is the st