How to Present Multi-Step Tasks According to i-have-adhd Rules

Multi-step tasks must be formatted as numbered lists where each entry represents a single, bounded action, starting with an immediate command and ending with a concrete next step that takes under two minutes.

The ayghri/i-have-adhd repository defines a specialized skill for producing ADHD-friendly output, with strict formatting rules designed to minimize cognitive load. When presenting multi-step tasks, the skill enforces a specific structure detailed in skills/i-have-adhd/SKILL.md that helps readers see progress, estimate time, and act without holding information in working memory.

The Core Rule for Multi-Step Task Presentation

According to Rule 2 in skills/i-have-adhd/SKILL.md, every multi-step task must use a plain numbered list. Each number represents one discrete action that the reader can complete before moving to the next item.

The rule explicitly forbids combining multiple actions into a single step using phrases like "and then" or comma-separated sequences. This constraint prevents the working memory overload that occurs when readers must track several sub-tasks simultaneously.

The Three-Step Structure for ADHD-Friendly Instructions

The i-have-adhd specification organizes multi-step task presentation into three mandatory components:

Lead with the Next Actionable Step (Rule 1)

The first line of any response containing multi-step tasks must be a concrete command the reader can execute immediately. This satisfies Rule 1 at line 33 of SKILL.md, which requires opening with an action rather than context or explanation.

Example:

1. Open `src/auth.ts` in your editor.

Number Each Bounded Action (Rule 2)

Each subsequent step follows the numbered list format mandated by Rule 2 at line 42. The specification requires:

• Single actions only: Each step must contain one executable task
• Minimalism: Omit unnecessary or trivial actions; fold small steps into the preceding one (line 46)
• No merging: Avoid conjunctions that link multiple operations

Correct format:

1. Open `src/auth.ts` in your editor.
2. Replace the `verifyToken` function (lines 42-58) with the snippet below.
3. Run the test suite for the auth module: `npm test -- auth.spec.ts`.

Incorrect format:

Bad: First open the file, find the function, swap it out, then run the tests.

Close with a Concrete Next Action (Rule 3)

Rule 3 at line 57 requires ending the multi-step sequence with a specific instruction telling the reader exactly what to do next. This final action should ideally require two minutes or less to complete, creating an immediate feedback loop that maintains momentum.

Example:

Next: Verify the tests pass and commit the changes (`git commit -m "Fix token verification"`).

Why This Format Works for ADHD Accessibility

The numbered list structure prescribed in skills/i-have-adhd/SKILL.md addresses specific executive function challenges:

• Progress visibility: Numbers create concrete checkpoints that combat task paralysis
• Time estimation: Bounded actions allow readers to gauge effort before starting
• Reduced load: Externalizing the sequence to the list prevents working memory failures
• Completion reward: Checking off each number provides dopaminergic feedback

Summary

• Multi-step tasks in the i-have-adhd framework must use numbered lists with one action per item.
• Rule 2 in skills/i-have-adhd/SKILL.md mandates single-bounded actions and forbids compound steps.
• Rule 1 requires starting with an immediate executable command, while Rule 3 demands ending with a sub-two-minute next action.
• The format eliminates "and then" constructions and folds trivial steps into larger ones.
• This structure supports ADHD readers by externalizing sequences and providing clear progress markers.

Frequently Asked Questions

What makes a step "bounded" according to the i-have-adhd rules?

A bounded step is a discrete action with a clear beginning and end that requires no further decision-making during execution. According to skills/i-have-adhd/SKILL.md, if you can complete the action without asking "what next?" until you finish, it is properly bounded. Examples include "Open the file" or "Run the test suite," whereas "Fix the bug" is unbounded because it contains undefined sub-steps.

Can I use bullet points instead of numbers for multi-step tasks?

No. The specification at line 42 of skills/i-have-adhd/SKILL.md explicitly requires numbered lists for multi-step tasks. Numbers provide the sequential structure and progress indication that bullet points lack, which is critical for readers who struggle with task initiation and sustained attention.

What happens if a task naturally has more than five steps?

The i-have-adhd rules do not set a maximum step count, but Rule 2 emphasizes minimalism and folding trivial steps. If a procedure exceeds what feels manageable, you should group related micro-actions into single bounded steps (e.g., "Configure the three environment variables in .env" rather than three separate "Add variable" steps) or break the task into smaller sub-tasks each with their own Rule 3 conclusion.

How strictly is the "under two minutes" rule for the final action enforced?

Rule 3 in SKILL.md mandates that the final concrete next action ideally takes under two minutes. This is a guideline to ensure the closing instruction is actionable rather than another large task that causes avoidance. If the natural next step requires more time, you should identify a smaller verification action (like "Check the output matches the expected format") that serves as the immediate next step before the larger task.

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