stage-0-framinglisted

Stage 0: framing. Load `method-rules` first; read `state.json` for the idea. Goal: a raw idea becomes a falsifiable hypothesis set, and we know exactly what must be tested first. This stage is elicitation + structuring — work WITH the user; your drafts are `[GUESS]` until they confirm or evidence backs them. Artifact templates: the `stage-0-framing-templates` skill. ## 0.0 Idea brief → `idea-brief.md` Before decomposing anything, complete the idea brief (created at new-idea; template in the `stage-0-framing-templates` skill): raw idea verbatim (immutable), refined articulation of **what it is**, for whom, **how it's imagined to work** (the solution concept), vision & rough roadmap (Blank: the first product spec comes from the founders' vision, and earlyvangelists buy the whole vision, not just v1 — so the vision must be written down: it is the thing this pipeline tests), why now / why this founder (reach, expertise, willingness to serve this segment daily), constraints, and the founder's definition of success. Elicit from the user; your drafts stay `[GUESS]`. The brief is a **living document** with an evolution log — every pivot the pipeline forces gets recorded there with its evidence trail. ## 0.0b Classify the intake, and rank what is actually blocking `[GUESS]` answers "is this backed yet?" — it does not answer "where did this come from?", and those are different questions at intake. Everything the founder said, and everything you read into it, goes into one compact t