Why Restating State Is Essential for ADHD-Friendly Communication

Restating the current state on every conversational turn compensates for limited working memory by providing a persistent, visible anchor that prevents readers from losing track of their progress in multi-step tasks.

The ayghri/i-have-adhd repository defines a structured communication framework designed specifically for interactions involving individuals with ADHD. At its core lies the "Restate state every turn" rule, documented in skills/i-have-adhd/SKILL.md, which mandates that assistants explicitly confirm the current step, recent progress, and immediate next action during every exchange.

The "Restate State Every Turn" Rule

According to the source code in skills/i-have-adhd/SKILL.md (lines 73-79), this rule requires that every response include a clear statement of where the user currently stands in a process. This practice transforms ephemeral conversation history into a self-contained progress log that remains readable without scrolling through previous messages.

The rule addresses a fundamental neurological constraint: working memory limitations mean that information not visible on screen is rapidly forgotten. By restating state, the assistant offloads the burden of tracking progress from the user's memory onto the visible interface.

Addressing Three Core ADHD Challenges

Restating state directly targets three specific executive function challenges common in ADHD:

1. Small working memory capacity — Keeping the current step number, recent actions, and next steps visible eliminates the need to hold this context mentally.
2. Difficulty transitioning from knowledge to action — Explicitly stating "Next: [specific action]" bridges the gap between understanding what needs doing and actually initiating the behavior.
3. Need for visible progress — Confirming what has been achieved (e.g., "Step 3 of 5 complete") provides dopaminergic feedback that maintains momentum and reduces abandonment risk.

Reducing Cognitive Friction

Without state restatement, users must reconstruct context by re-reading previous messages, creating cognitive friction that increases the likelihood of task abandonment. The i-have-adhd skill eliminates this overhead by ensuring each message contains sufficient context to act upon immediately.

This approach acknowledges that in ADHD cognition, out of sight is out of mind. When a conversational thread spans multiple turns, the reader cannot reliably remember which step they are on or what has already been accomplished unless explicitly reminded.

Practical Implementation Examples

The repository provides concrete examples contrasting ineffective communication with the ADHD-friendly style.

Incorrect style without state restatement:

Run `npm install jsonwebtoken@latest`. Then edit the file, run tests, and let me know if it works.

Correct style with explicit state restatement:

Step 1 of 3 – Initialize

Run `npm install jsonwebtoken@latest`.

Step 2 of 3 – Edit

Open `src/auth.ts` and replace the `verifyToken` function (lines 42-58) with the new snippet.

Step 3 of 3 – Validate

Execute `npm test -- auth.spec.ts`.
Next: paste the first failing line if any test fails.

The corrected version provides a lightweight, scannable progress log that requires no working memory to parse.

Repository Structure and Implementation

The rule is implemented across three key files in the ayghri/i-have-adhd repository:

• skills/i-have-adhd/SKILL.md — Defines the "Restate state every turn" rule (lines 73-79) and provides behavioral specifications.
• README.md — Summarizes all 10 communication rules, with particular emphasis on rule 5 regarding state restatement.
• AGENTS.md — Details how the skill integrates into various AI runtimes while maintaining state-restating behavior.

Summary

• Restating state compensates for ADHD-related working memory limitations by ensuring current progress remains visible without scrolling.
• Explicit step numbering and next-action statements reduce the cognitive friction associated with task initiation and continuation.
• Self-contained messages act as persistent anchors that prevent users from losing track of multi-step processes.
• The i-have-adhd skill codifies this as rule 5 in SKILL.md, requiring explicit confirmation of completed steps and immediate next actions on every turn.
• Visible progress tracking helps maintain dopaminergic momentum, significantly reducing task abandonment rates.

Frequently Asked Questions

What does "restating state" mean in the context of ADHD communication?

Restating state means explicitly mentioning the current step number, what was just accomplished, and the immediate next action at the beginning of every conversational turn. According to SKILL.md, this practice ensures that each message contains sufficient context to be understood in isolation, without requiring the reader to remember previous exchanges.

How does restating state help with ADHD working memory limitations?

People with ADHD typically have reduced working memory capacity, meaning information disappears from conscious awareness when it leaves the screen. By restating the current state on every turn, the assistant provides a persistent visual anchor that offloads memory requirements from the user to the interface, preventing disorientation in multi-step tasks.

Can restating state actually improve task completion rates for people with ADHD?

Yes. Restating state reduces cognitive friction by eliminating the need to reconstruct context from previous messages. It also provides visible progress indicators (e.g., "Step 2 of 4 complete"), which deliver necessary dopaminergic feedback that helps sustain motivation through task completion, directly addressing the ADHD tendency toward abandonment of multi-step processes.

Where is the restating state rule documented in the i-have-adhd repository?

The rule is formally defined in skills/i-have-adhd/SKILL.md at lines 73-79, referenced as rule 5. It is also summarized in the README.md alongside nine other communication guidelines, with implementation details available in AGENTS.md for runtime integration.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}