adhd

name	adhd
description	Use when parallel divergent ideation for agents — spawns N isolated reasoning branches under different cognitive frames, then scores, clusters, prunes traps, and deepens survivors. Use for open-ended design, architecture, naming, API surface decisions, fuzzy debugging, and brainstorming. Skip for syntax lookups or bugs with known root cause.
domain	core
author	mahipal
license	MIT
subdomain	reasoning
tags	["reasoning","brainstorming","decision-making","cognitive-frames","divergent-thinking","architecture","design"]
version	1.0.0

persona: name: "Udit Akhouri" title: "The Divergent Ideation Architect" expertise: ['Parallel Reasoning Architectures', 'Cognitive Frames', 'Agent Skill Design', 'Premature Convergence'] philosophy: "The first three answers are the ones a senior engineer gives in thirty seconds. Correct. Forgettable. The interesting answers live past number three." credentials: ['Author of ADHD preprint', 'Creator of adhdstack.github.io', 'MIT-licensed open source'] principles: ['Isolate before converge', 'Generator and critic must never mix', 'Structure is half the value', 'Expensive — gate before use']

ADHD — Parallel Divergent Ideation

Upstream: github.com/UditAkhourii/adhd
License: MIT
Preprint: adhdstack.github.io

Stop picking the textbook answer. This skill forces the agent to walk into the awkward middle where non-obvious solutions live.

---

When to Use

Trigger phrases:

• "/adhd"
• "ADHD mode"
• "use parallel ideation"
• "brainstorm this"
• "give me a few ways to..."
• "think outside the box on this"

Use when:

• Architecture decisions where the obvious answer may not be best
• API/SDK surface design (naming, ergonomics, DX tradeoffs)
• Naming things (products, features, variables, endpoints)
• Fuzzy debugging with no known root cause
• Open-ended strategy or positioning
• Schema / data model design

Don't use for:

• Syntax lookups ("what's the Python equivalent of...")
• Bugs with a known root cause
• Any question with one canonical answer
• Low-stakes decisions ("what color should this button be?")
• When the user says "quick", "standard", "canonical", "textbook", or "just"

---

How to Use

1. Confirm fit — Check the task against the trigger phrases and "Use when" list; bail if it hits "Don't use for"
2. Enter The Loop — Run the parallel ideation loop below (Diverge → Focus), phases gate on their own inputs
3. Apply cognitive frames — Use the frames section to stretch or prune candidate directions
4. Pick and commit — Converge on one direction and exit the loop; do not re-open decisions without new information
5. Verify — Run the Verification Checklist before shipping the chosen design