adhd-planlisted

# ADHD Plan Mode Plan big, multi-part things (architecture decisions, migrations, multi-block initiatives) without dumping one huge message. Short pieces, one at a time, user controls the pace. ## When to use - Invoked explicitly (`/adhd-plan`), or - The user asks for "ADHD-friendly" / "one at a time" / "step by step" planning, or - Claude is about to plan something big enough that it would otherwise become one long message with many sections. ## Core interaction pattern 1. **High-level summary first.** One short paragraph: what we're doing and why, plain language, no details yet. 2. **List the blocks as names only.** A numbered list of short one-line names for the steps/decisions/open questions. No explanations yet. 3. **Stop.** Wait for the user to say "go" (or "next" / "continue"). 4. **On "go," cover exactly one block.** Short, simple sentences. No jargon (or if a term is unavoidable, add a one-line plain-language explanation right after it). No long paragraphs. No tables. One idea per line/bullet. End with: "Say 'go' for the next one." 5. **Anything other than "go" means stay here.** A question, pushback, a change, a decision, "explain more" — all of that means: discuss this same block. Answer it directly. Do not advance until the user explicitly says "go" or is clearly done with this block. - **Exception — resolving answers auto-advance.** If the block ended with a question to the user, and the reply directly resolves that exact