Best Practice for Numbering Multi-Step Tasks with I-Have-ADHD

Number each step as a single, bounded action without "and then" statements, placing commands before explanations to minimize cognitive load.

The ayghri/i-have-adhd repository defines a strict convention for breaking down complex work into manageable pieces. Following the numbering multi-step tasks with I-Have-ADHD methodology ensures readers can track progress without holding multiple context pieces in working memory. The canonical rules reside in skills/i-have-adhd/SKILL.md and are summarized in README.md.

Core Numbering Rules in SKILL.md

The authoritative guidelines live in skills/i-have-adhd/SKILL.md between lines 42‑55. The specification states: "If the work takes more than one step, write a numbered list. Each step is one bounded action. No step contains 'and then' twice."

Enforce Single Bounded Actions

Each numbered item must represent exactly one concrete operation. This constraint prevents the cognitive overload that occurs when readers must parse multiple verbs within a single list element. Combine only trivial actions into the preceding step, and remove any steps that are not strictly necessary.

Eliminate "And Then" Constructions

The rule explicitly forbids sequential conjunctions within a step. When you write "and then" or "then" inside a step, you have violated the single-action boundary and created a hidden sub-list that forces the reader to maintain multiple mental checkpoints.

Prioritize Commands Over Prose

Present terminal commands, file paths, or code snippets first in each step, followed by brief explanatory text. This command-first approach allows readers to execute immediately while skimming details only if needed.

Anti-Patterns vs. Correct Implementation

The Multi-Action Trap (Bad Example)

1. Open the file, find the function, replace it, then run the tests.

This violates the SKILL.md specification by containing three distinct actions and using the forbidden "then" construction. Readers cannot estimate effort or track completion mid-step.

Compliant Numbering (Good Example)

1. Open `src/auth.ts`.
2. Replace `verifyToken` (lines 42-58) with the new snippet.
3. Run `npm test -- auth.spec.ts`.

Each line contains one bounded action. Commands appear first. No step contains "and then." This format allows readers to see what to do now, estimate the effort, and track progress without working memory strain.

Cognitive Rationale Behind the Format

The README.md summarizes ten rules governing ADHD-friendly documentation, while INSTALL.md provides installation steps that demonstrate the numbering style in practice. The system specifically addresses executive function limitations by externalizing task sequences. By minimizing the total number of steps and eliminating compound actions, the format reduces the cognitive load required to initiate and complete work.

Summary

• Use simple numbered lists in SKILL.md format when work requires multiple actions.
• Restrict each step to a single bounded operation without "and then" constructions.
• Place commands first, followed by minimal explanatory prose.
• Minimize total steps by combining only trivial actions and removing unnecessary ones.
• Reference lines 42-55 of skills/i-have-adhd/SKILL.md for the canonical rule definition.

Frequently Asked Questions

Where are the numbering rules defined in the repository?

The authoritative specification resides in skills/i-have-adhd/SKILL.md at lines 42‑55. The README.md provides a high-level summary of all ten rules, while INSTALL.md demonstrates practical application of the numbering format.

Can I combine small related actions into one step?

Only if the actions are trivial and inseparable. The guideline emphasizes minimizing the total number of steps, but never at the cost of introducing "and then" constructions or multiple distinct operations within a single numbered item.

How do I handle conditional branches in the numbering?

The source analysis does not specify notation for conditional logic. Generally, avoid embedding optional paths within the main sequence; instead, create a separate sub-list or note appended to the relevant primary step, ensuring the main numbered list remains a mandatory path.

Does this format work for non-coding tasks?

Yes. While the examples in INSTALL.md and SKILL.md use file paths and terminal commands, the underlying principle—single bounded actions without sequential conjunctions—applies to any multi-step process requiring sustained attention.

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