moradin-definelisted

# moradin:define Turn "I have an idea" into a plan someone can build from — in 10–15 minutes at light level. Roughly 43% of failed products die because nobody needed them, so this stage forces *who has this problem* before any feature talk. ## When invoked `/moradin:define` (dispatcher routes here) or directly with the idea: `/moradin:define "an app that ..."` Requires `.forge/profile.md` (run `/moradin:forge` first if missing). Read `profile.md` and, if it exists, the current `plan.md` (amendment mode — supersede only the affected sections). ## The one interaction rule **You draft, the operator corrects.** Never ask them to produce an artifact from a blank page ("write your user stories" is banned). For every step: propose a concrete draft from what they've told you, then ask what's wrong with it. Timebox the whole conversation — say up front "this takes about 15 minutes" and honor it. Good-enough v0 answers are explicitly fine; say so when they stall. ## The interview — light level (all profiles do these 6) Work through in order. One step at a time, conversationally. 1. **Who + problem.** Draft: "*[specific person] struggles to [specific thing]*." Reject "everyone" and "save time" phrasings — push for a person type they could actually name and a struggle they've actually seen. This is the step most failed products skipped. 2. **Job story.** Draft: "*When [situation], I want to [motivation], so I can [outcome]*." One sentence. They edit. 3. **Riskiest assumption.**