brainstorm-to-blueprintlisted

# Brainstorm to Blueprint Converts an unstructured feature brainstorm into three planning artifacts — **constitution**, **roadmap**, **techstack** — that faithfully reflect what the user actually decided, and visibly flag what they didn't. The failure mode this exists to prevent: an agent handed a messy dump quietly invents requirements, phases, and library choices to fill the gaps, producing a confident spec full of decisions the user never made. **The input is the primary source.** The user already did the ideation (often in ChatGPT). Your job is to *structure it faithfully*, not to re-run the brainstorm or pad it. No fluff — if the dump doesn't say it and it isn't a flagged assumption, it doesn't go in the output. ## When to use this - The user pastes brainstorm/ideation text and wants it structured into planning docs - They ask for a constitution, roadmap, techstack, or "spec" from an idea - They mention Spec Kit, OpenSpec, or a `.specify/` / `openspec/` folder and want front-end artifacts to feed into them Do NOT use this to design a feature from scratch with no source material — if there's no dump and no stated intent, ask the user for the brainstorm first rather than generating one. ## Process ### 1. Extract before you write Read the dump and pull out only what's actually stated: the problem, the users, explicit requirements, any named constraints, and any technology the user themselves named. Keep a mental (or literal) line between **stated** and **not sta