devlynideatelisted

Spec-elicitation surface for users who have ideas but not engineering specifications. AI drives the conversation with focused questions until a structurally-valid, verifiable spec exists. Output consumed directly by `/devlyn:resolve --spec`. <elicit_config> $ARGUMENTS </elicit_config> <orchestrator_context> This skill is OPTIONAL. `/devlyn:resolve` is standalone-capable: free-form mode handles trivial/medium tasks without a spec, `--spec` mode accepts handwritten specs from any source. Use ideate when the user wants AI to do the elicitation work. </orchestrator_context> <elicitation_contract> The user does not know context engineering. They will under-specify and over-assume. AI's job is to ask focused, specific questions that surface the missing engineering decisions. 1. Ask one or two questions per turn, not more. Multi-question lists overwhelm and produce shallow answers. 2. Questions are concrete and decision-grade — what is the input, what is the expected output, what command verifies success, what files are out of scope. 3. Do not ask design preferences the user clearly does not have. Infer the simplest reasonable default and confirm in one line. 4. Stop when the spec passes structural lint AND the user explicitly confirms or 8 turns have elapsed (whichever comes first). Eight turns is a hard ceiling — beyond that, the spec is either ready or the task is too large for ideate. 5. The output is the spec, not a transcript. Do not include the conversation in the saved f