blueprintlisted

# blueprint Take a new thing from fuzzy idea to a design worth executing. The premise (*the pattern is in the threading*): outcomes are mostly decided by choices made before building starts — so spend real effort there, once, and produce ONE artifact a fresh session can execute from cold. The whole skill in one breath: **frame it in a sentence, explore wider than instinct, commit to one shape and defend the pick, attack it before reality does, ship a doc with a kill switch.** Compose, don't reinvent: if you have companion skills for mental-model lenses, structured research, or premortems, route through them rather than duplicating them here. ## GATE Blueprint only what's expensive to reverse or genuinely novel. Known-shape feature or obvious build → plan mode or just build. Repeatable output type → build a pipeline skill for it. Murky "something is wrong" diagnosis → a diagnosis pass, not a blueprint. Say which and stop. Design depth scales with cost of change (Fowler, verified): where tests + CI make change cheap, skipping design is licensed — where change is expensive (data models, public interfaces, hardware, money), it isn't. "Skip upfront design" is a privilege earned by cheap-change infrastructure, never a default. ## FRAME — converge on what this is **Through-line.** One sentence, zero jargon (Heilmeier's first question): what this really is, for whom, and what changes in the world when it exists. Everything downstream is tested against it. Can't write the sent