How the i‑have‑adhd Skill Numbers Multi‑Step Tasks

The i‑have‑adhd skill enforces a strict numbering convention using plain Arabic numerals (1., 2., 3.) where each list item represents exactly one atomic, independently executable action.

The i‑have‑adhd skill is an open-source framework designed to make AI-assisted workflows more accessible for users with ADHD. One of its core conventions is how it handles multi-step task numbering — a rule that breaks complex work into discrete, manageable chunks. According to the source code in ayghri/i-have-adhd, this numbering system appears in skills/i-have-adhd/SKILL.md and is mirrored for the Cursor harness at .cursor/skills/i‑have‑adhd/SKILL.md.

The Numbering Rules for Multi-Step Tasks

The skill's numbering convention follows four strict requirements defined in SKILL.md under section "### 2. Number multi‑step tasks" (lines 44‑57):

• One step per line — each numbered item must describe exactly one action that can be executed independently.
• Minimal steps — include only essential actions; trivial steps are folded into the preceding one.
• No "and then" chaining — a single step must not contain multiple sequential actions; keep each step atomic.
• Use plain numbers — format the list with Arabic numerals (1., 2., 3., …), not letters or other schemes.

The documentation provides explicit "bad" vs. "good" examples to illustrate this format (lines 50‑57).

Correct vs. Incorrect Numbering Examples

Bad Example: Multiple Actions in One Step

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

This violates the atomicity rule by chaining multiple actions with "and then" phrasing.

Correct Example: Each Step Isolated

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

Each step here is self-contained and executable without parsing multiple sub-actions.

Integration with Task-or-Plan Tools

When the harness (such as Cursor or OpenAI's tool) supports a task-or-plan interface, the skill leverages this checklist mechanism to automatically restate the current step. As implemented in skills/i-have-adhd/SKILL.md (lines 82‑83), this ensures the reader always knows which numbered item is active, reducing cognitive load and context-switching friction.

Where the Numbering Rules Are Defined

File	Purpose
skills/i-have-adhd/SKILL.md	Primary definition of the multi-step task numbering rule and examples
.cursor/skills/i-have-adhd/SKILL.md	Mirror of the same rule for the Cursor harness (identical content)
README.md (section "2. Number multi‑step tasks")	High-level reference to the rule in the repository overview (line 91)

All three files maintain consistency in how multi-step tasks are numbered, ensuring the convention applies regardless of which harness executes the skill.

Summary

• The i‑have‑adhd skill uses plain Arabic numerals (1., 2., 3.) for all multi-step tasks.
• Each numbered item must contain exactly one atomic action — no "and then" chaining allowed.
• Trivial actions are folded into preceding steps to keep the list minimal.
• The task-or-plan tool integration automatically highlights the current step when available.
• Core definitions reside in skills/i‑have‑adhd/SKILL.md and its Cursor mirror.

Frequently Asked Questions

What number format does the i‑have‑adhd skill require for multi-step tasks?

The skill requires Arabic numerals with periods: 1., 2., 3., and so on. This format appears in skills/i-have-adhd/SKILL.md lines 44‑57 and is enforced consistently across all skill implementations.

Can a single step contain multiple related actions?

No. The i‑have‑adhd skill explicitly forbids "and then" chaining within a step. Each numbered item must describe one independently executable action. Multiple actions must be split into separate numbered items.

How does the skill handle step tracking during execution?

When the harness supports it, the skill uses a task-or-plan tool checklist to automatically restate the current step (lines 82‑83 of SKILL.md). This keeps the user oriented without manual tracking.

Where is the numbering rule documented in the repository?

The primary documentation is skills/i-have-adhd/SKILL.md under the "### 2. Number multi‑step tasks" section. An identical mirror exists at .cursor/skills/i-have-adhd/SKILL.md for Cursor users, and the README.md references the rule at line 91.

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