ideatinglisted

# Ideating Three activities with very different footprints: quick capture (zero friction), dialogue-driven ideation (expand thinking), and idea review (decide what to pursue). Match the activity to what the user brings — and keep capture frictionless above all. Skip this skill when the user already knows what they want (`understanding-the-ask`) or is evaluating a specific solution (`solutioning`). ## Activity 1 — Quick capture The user has a thought and wants it preserved before it vanishes. 1. Accept whatever is given — a phrase, a sentence, a question. 2. Append to the project's `ideas.md` with the date and a one-line summary (format below). 3. Confirm saved, move on. No forced formality: if the user says "quick idea: versioned skills", write exactly that. Don't expand, structure, or ask clarifying questions unless the user wants dialogue. ## Activity 2 — Dialogue-driven ideation Frame the exploration first — "What are we exploring? Starting fresh, or building on something?" A rough focus is enough; it doesn't need to be a problem statement. Pick facilitation techniques to fit, and use them naturally without naming them ("What if we looked at this from a purely emotional perspective?", not "Now we're using Red Hat thinking"): - **Expansive exploration** — SCAMPER prompts (substitute? combine? adapt?), analogies from other domains, random connections - **Perspective-shifting** — Six Thinking Hats lenses, stakeholder viewpoints, "How might we" questions - **Assumpti