write-idealisted

# Write Idea Turn a raw idea into `docs/specs/<slug>/_idea.md` — the Stage 0 artifact that answers "should we build this, and in what shape?" before `write-prd` answers "what exactly are we building?". The idea stage exists because unexamined business assumptions are the cheapest thing to fix here and the most expensive thing to fix after tasks are cut. ## When this stage earns its cost Use it for product-level ideas: greenfield features, ideas with real market/competitive questions, or anything where the right _shape_ of the solution is still open. For a well-understood feature in a known area, say so and go straight to `grilling`/`grill-with-docs` → `write-prd` — a full idea study of an obvious feature is ceremony, not insight. ## Ground rules - **Read `CONTEXT.md` first** and keep its vocabulary; new terms this idea coins get sharpened and added to the glossary as they're resolved. - **One question per message**, multiple-choice with a suggested default whenever options are enumerable (`D) Other — describe` as the escape). 3–6 questions total; stop early if answers show the idea is already well-defined. - **WHAT, WHY, WHO only.** Databases, APIs, frameworks, and architecture are forbidden topics here — they belong to `write-techspec`. - **Research before writing.** Never draft an idea unbacked by codebase findings and (for user-facing ideas) market data. - **Reference adopted sources at their owned path.** When a source already belongs to an active or archived Spec,