i-have-adhd Time Estimate Format: How to Write Precise Durations for ADHD Planning

The i-have-adhd skill requires all time estimates to use concrete numerical units (minutes, hours, days) and explicitly prohibits vague phrasing like "a bit" or "some work."

The ayghri/i-have-adhd repository defines a structured approach to time estimation designed specifically to support readers with ADHD. Clear, actionable timeframes reduce decision paralysis and help users break tasks into manageable chunks. Understanding the exact format requirements ensures compliance with the skill's guidelines.

The Core Rule: Specific Time Estimates Only

Rule 6 in the i-have-adhd skill mandates specific time estimates expressed in concrete units. According to skills/i-have-adhd/SKILL.md (lines 84-90), estimates must use minutes, hours, days, or other measurable time units.

The rule appears across multiple configuration files:

• README.md (lines 94-95): Summarizes the requirement as "Specific time estimates (minutes, not 'a bit')"
• skills/i-have-adhd/agents/gemini.toml (line 15): Reiterates the same wording for the Gemini agent configuration

Required Format Elements

A compliant i-have-adhd time estimate must satisfy three criteria:

1. State the unit explicitly — Use "minutes," "hours," "days," or equivalent
2. Eliminate ambiguous adjectives — No "a bit," "some time," "a while," or "soon"
3. Provide concrete ranges when uncertain — Offer bracketed alternatives rather than leaving timing open-ended

Correct Format Example

The authoritative example from SKILL.md follows this pattern:

About 15 minutes if tests already cover this. An afternoon if not.

Practical Code Examples

Valid Time Estimate in a Task List

1. Open `src/auth.ts`…
2. Replace the `verifyToken` function.
3. Run `npm test`.
⏱️ About 12 minutes if tests already exist; up to 30 minutes if you need to write new tests.

This example demonstrates the range pattern: base estimate + conditional alternative.

Invalid (Vague) Time Estimate

⏱️ A bit of work.

This violates Rule 6 by using the prohibited phrase "a bit" without any numerical unit.

Larger Task Using Hours

⏱️ Roughly 2 hours to refactor the middleware and update the documentation.

Hours are appropriate for tasks exceeding 45-60 minutes, maintaining the concrete unit requirement.

Implementation Across the Repository

The time estimate rule propagates through several key files in the ayghri/i-have-adhd codebase:

File	Purpose
skills/i-have-adhd/SKILL.md	Contains the authoritative Rule 6 definition and canonical examples
README.md	High-level summary for repository visitors
skills/i-have-adhd/agents/gemini.toml	Agent-specific reinforcement of the requirement

Summary

• The i-have-adhd time estimate format requires numerical values with explicit units (minutes, hours, days)
• Vague qualifiers are prohibited: "a bit," "some," "a while," and similar phrasing break compliance
• Conditional ranges are encouraged when task duration varies based on circumstances
• The rule originates in SKILL.md and propagates through agent configurations like gemini.toml

Frequently Asked Questions

What units are acceptable for i-have-adhd time estimates?

Minutes, hours, days, and any other concrete time measurement are acceptable. The critical requirement is specificity—"15 minutes" complies; "a short time" does not.

Can I use approximate phrasing like "roughly" or "about"?

Yes. Approximate indicators such as "about," "roughly," or "approximately" are permitted when paired with numerical units. "About 15 minutes" is valid; "about a while" is not.

Why does i-have-adhd prohibit vague time estimates?

Vague duration phrasing creates ambiguity for ADHD planners, increasing cognitive load and decision paralysis. Concrete estimates transform abstract tasks into actionable, time-boxed commitments.

Where is the time estimate rule officially defined?

The authoritative definition resides in skills/i-have-adhd/SKILL.md (lines 84-90), with secondary references in README.md and skills/i-have-adhd/agents/gemini.toml.

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