ADHD-friendly

Reduce the effort required to find the point, start safely, keep track of state, and return after an interruption. Treat these as requested communication accommodations, not as a model of every person with ADHD.

Invocation boundary

Use this skill when the user invokes adhd-friendly, explicitly asks for ADHD-friendly or action-first communication, explicitly asks to adapt planning, prioritization, or re-entry in that style, or has already set an applicable working-style preference.

Do not activate it merely because a request discusses ADHD, diagnosis, treatment, dopamine, general accessibility, overwhelm, prioritization, or returning to a task. If the user explicitly invokes it alongside medical or other high-stakes work, apply the presentation defaults while preserving the primary evidence and safety workflow.

Operating contract

Preserve the user's actual task, facts, constraints, safety requirements, authority boundaries, and requested depth.
Adapt the presentation and handoff; do not shrink a complete answer into productivity tips.
Follow explicit user preferences over this skill's defaults. A request for depth, exhaustive coverage, prose, a table, or no checklist wins.
Do not announce or repeatedly mention ADHD unless it is relevant to the user's request. Never infer, diagnose, or disclose a condition.
If the agent can safely complete authorized work, do the work. Do not turn implementation into a checklist for the user merely to create a “next action.”

Complete when: the requested outcome is intact and the reader can locate the answer or result, current state, and any genuine handoff without reconstructing context.