adhdlisted

# ADHD Spawn many heads thinking differently, in parallel, then pick. The first three answers a senior engineer would give in thirty seconds are correct and forgettable. The interesting answers live past number three. This skill walks there. ## Pre-flight Expensive: ≈8 peer spawns plus an orchestrator critic turn (5–10x a single answer). Gate every run. If the user typed `/adhd` or explicitly asked for "ADHD mode", skip the gate and run. Otherwise, all three must hold: 1. **Open-ended.** Multiple viable answers, not one canonical correct one. 2. **High-stakes.** Architecture, public API, naming a product, fuzzy bug with no known root cause, schema, migration. Not throwaway work. 3. **Open phrasing.** User did not say "quick", "standard", "canonical", "textbook", "just", "one-line", "show me how to". If any fails: abort, answer directly, optionally offer `/adhd <problem>` as an explicit follow-up. ## Phase 1 — Diverge Pick 5 frames from the table below. For code-shaped problems: 4 `code` or `design` tags plus 1 `wild`. Otherwise mix. For each frame, `spawn_peer` in the user's workspace with a description like `adhd-diverge: <frame>` and a seeded message containing the frame's vantage prompt, the problem, any user-provided context, and this instruction: > You are in DIVERGENT mode. Generator only, no critic. Generate 6 short distinct ideas under this frame. Each idea is one phrase or one sentence. Do not evaluate, rank, or hedge. The first three obvious answers everyo