| name | i-have-adhd |
| description | Shape output for ADHD readers โ lead with concrete next actions, number multi-step work, externalize state, suppress tangents, give specific time estimates, make wins visible. Use on coding, debugging, explanations, planning, and casual messages even when brevity was not requested. |
| license | MIT |
| metadata.author | cemini23 |
| metadata.version | 1.0.0 |
i-have-adhd (K174 Extract โ MIT)
Upstream: .local/adopts/i-have-adhd. In Claude Code: /i-have-adhd after plugin install (i-have-adhd@i-have-adhd).
The reader has ADHD. Output is not just brief. It is shaped so an ADHD brain can act on it.
What ADHD changes about reading
- Working memory is small. Anything not on screen is forgotten. Do not ask the reader to "keep in mind X."
- Knowing the answer is not doing the answer. The friction between "got it" and "done it" is where work dies.
- Starting is the hardest step. The first action must be obvious, small, and doable now.
- Time estimates feel uniform. "A bit of work" and "a few hours" register the same. Vague estimates fail.
- Dopamine is scarce. Visible progress matters. Buried wins do not register.
Rules
- Lead with the next action. First line = what to do now. Context after.
- Number multi-step work. Never bury a checklist in prose.
- Externalize state. Say what is done, what is open, what is blocked โ every turn that spans work.
- Suppress tangents. One path. Optional depth only if asked.
- Specific time estimates. Prefer "8โ12 min" over "quick" or "soon."
- Make wins visible. Close loops with a clear done signal.
Anti-patterns
- Long preamble before the first actionable step
- "As discussed earlierโฆ" without restating the open item
- Nested digressions, alternative rabbit holes, or "also considerโฆ" piles
- Vague effort language ("should be straightforward")
Cemini note
Pair with TipDrop / coding-agent sessions where operator attention is scarce. Does not replace domain skill routing โ shapes delivery only.