Time Estimates Preferred by the i-have-adhd Skill: A Complete Guide

The i-have-adhd skill requires concrete, numeric time estimates expressed in minutes (e.g., "≈ 15 minutes") and rejects vague phrases like "a bit of work" or "a few hours" to help users with ADHD plan actionable steps.

The ayghri/i-have-adhd repository defines a specialized skill designed to accommodate cognitive patterns associated with ADHD. Understanding the specific time estimate format preferred by this skill ensures that generated responses help users gauge effort accurately and overcome task initiation barriers.

Why Concrete Time Estimates Matter for ADHD Planning

Vague temporal language creates planning paralysis for individuals with ADHD. When estimates are abstract, the brain registers "a few hours" and "a bit of work" identically—both feel ambiguous and overwhelming. The i-have-adhd skill addresses this by enforcing ball-parked concrete units that allow immediate judgment about whether a task fits the current available window.

According to the source code, the skill explicitly treats vague phrasing as anti-patterns because they fail to support executive function needs. Specific minute-based estimates transform abstract obligations into quantifiable, approachable units.

The Rule as Defined in the Source Code

The requirement for concrete time estimates appears in two canonical locations within the repository, each serving different documentation purposes.

README.md Rule 6 (High-Level Summary)

In README.md at line 75, the sixth rule of the skill states:

Specific time estimates (minutes, not 'a bit')

This high-level directive establishes the fundamental constraint: all duration references must use numeric minute values rather than colloquial English expressions.

SKILL.md Detailed Specification (Lines 82-88)

The canonical skills/i-have-adhd/SKILL.md file expands this requirement significantly between lines 82-88. This document provides the detailed rule specification, including explicit "Bad" versus "Good" examples that demonstrate the preferred formatting style. The specification emphasizes that estimates must be specific and expressed in concrete units, ensuring users can quickly decide whether they possess the cognitive bandwidth to start the task immediately.

Good vs. Bad Time Estimate Examples

The skill distinguishes sharply between acceptable and unacceptable formats. Below are concrete examples derived from the repository's specifications.

Good time-estimate usage (as the skill would generate):

1. Open `src/auth.ts`                     # 1 minute

2. Replace the `verifyToken` function      # 5 minutes

3. Run `npm test -- auth.spec.ts`          # 3 minutes

Bad time-estimate usage (to avoid):

This will take some work.   # ❌ vague

Embedding a time estimate in a single-step response:

Run `npm install jsonwebtoken` now – about **2 minutes**.

Implementation Guidelines

When implementing responses compatible with the i-have-adhd skill, follow these formatting standards to ensure compliance with the concrete time estimate rule.

Formatting Numeric Estimates

Always express durations as integers with the unit "minutes" explicitly stated or clearly implied. Use the approximate symbol (≈) or the word "about" to indicate ball-parking, but never omit the number. Acceptable formats include:

• ≈ 15 minutes
• about 2 minutes
• # 5 minutes (when appended as a comment in code blocks)

Avoid ranges like "5-10 minutes" which introduce decision fatigue; instead, pick a conservative single number.

Embedding Estimates in Task Lists

When generating numbered task lists—common in technical instructions—append the time estimate as a right-aligned comment using the # symbol followed by the duration. This pattern, demonstrated in SKILL.md, keeps the task description clean while providing the critical temporal context needed for ADHD planning.

Summary

• The i-have-adhd skill mandates concrete, numeric time estimates expressed in minutes, not vague English phrases.
• Rule 6 in README.md (line 75) establishes the high-level requirement for specific estimates.
• Detailed specification and examples exist in skills/i-have-adhd/SKILL.md (lines 82-88), showing "Bad" vs. "Good" formatting.
• Vague phrases like "a bit of work" or "some time" register as ambiguous obstacles to users with ADHD and must be eliminated.
• Best practice involves appending estimates as minute counts in task lists or bolding them within narrative text.

Frequently Asked Questions

What makes a time estimate "vague" according to the i-have-adhd skill?

Vague estimates include phrases like "a bit," "a few hours," "some work," or "later today." The skill classifies these as anti-patterns because they lack numeric specificity. According to the SKILL.md specification, only estimates with concrete minute values (e.g., "3 minutes," "15 minutes") provide the executive function support required for ADHD planning.

Can I use hour-based estimates instead of minutes?

The skill prefers minutes for durations under an hour to maintain granularity. While hours might be acceptable for very long tasks, the repository examples consistently use minutes (e.g., "5 minutes" rather than "0.08 hours"). Minutes align better with the cognitive chunking strategies recommended for ADHD task management.

Where is the time estimate rule documented in the repository?

The rule appears in two locations: README.md at line 75 provides the concise "Rule 6" summary stating "Specific time estimates (minutes, not 'a bit')", and skills/i-have-adhd/SKILL.md between lines 82-88 contains the detailed specification with formatting examples and rationale for why concrete units matter.

How should time estimates be formatted in code block responses?

Append the estimate as a comment at the end of the line using the # symbol followed by the duration (e.g., # 5 minutes), or embed it in the narrative using bold text (e.g., "2 minutes"). The SKILL.md file demonstrates both patterns: right-aligned comments in numbered lists and inline bold formatting for single-step instructions.

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