# Time Estimate Format in the i-have-adhd Skill: A Complete Guide

> Learn the exact time estimate format for the i-have-adhd skill. Discover how to use explicit units like minutes and hours for clear task management.

- Repository: [Ayoub Ghriss/i-have-adhd](https://github.com/ayghri/i-have-adhd)
- Tags: api-reference
- Published: 2026-09-02

---

**The i-have-adhd skill requires concrete, unit-based time estimates expressed in explicit units such as minutes, hours, or days, avoiding vague phrasing like "a bit of work" or "soon."**

The `ayghri/i-have-adhd` repository provides a specialized skill designed to reduce friction for ADHD-focused users by enforcing specific communication patterns. One of the most critical patterns is how **time estimates** must be formatted in any task the skill suggests. This guide explains the exact format, where it's defined, and how to apply it correctly.

## Where the Time Estimate Rule Is Defined

The time estimate requirement is formally specified in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) at lines 82-88, under section "### 6. Give specific time estimates". According to the skill specification, every task must include a **concrete, unit-based time estimate** rather than ambiguous duration descriptions.

This rule ensures readers can immediately assess whether they have the bandwidth to start a task—removing the decision paralysis that vague estimates create.

## The Three Rules for Time Estimate Format

The i-have-adhd skill enforces three consistent formatting principles:

1. **Start with a concrete unit** — Use explicit measurements like "15 minutes", "2 hours", or "an afternoon".

2. **Optionally qualify with conditions** — Add context such as "if tests already cover this" or "assuming no external dependencies".

3. **Avoid vague descriptors** — Never use phrases like "a bit of work", "some time", "soon", or "later".

## Valid Time Estimate Examples

The following examples from [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) demonstrate correctly formatted estimates:

**Good time estimates:**

```markdown
- "About 15 minutes if the test suite is already passing."
- "Approximately 2 hours to refactor the authentication module."
- "An afternoon to redesign the landing page."

```

**Bad time estimates (rejected by the skill):**

```markdown
- "This will take some work."
- "A bit of effort later."

```

## Embedding Time Estimates in Step Lists

When breaking tasks into numbered steps, maintain the same concrete format by appending the estimate to each action:

```markdown
1. Open `src/auth.ts` – **5 minutes**.
2. Replace `verifyToken` with the new snippet – **10 minutes**.
3. Run `npm test -- auth.spec.ts` – **3 minutes**.

```

This inline formatting keeps effort visible at every decision point, which aligns with the skill's goal of reducing cognitive load for ADHD users.

## Why This Format Matters for ADHD-Focused Work

The i-have-adhd skill's time estimate format serves a specific psychological function. Concrete units externalize time judgment—users don't need to interpret what "a bit" or "soon" means relative to their current energy state. By standardizing on **minutes, hours, and days**, the skill removes ambiguity that typically triggers procrastination loops.

As implemented in `ayghri/i-have-adhd`, this rule is non-negotiable. The skill specification explicitly rejects estimates without measurable units, ensuring consistent output across all tasks generated under its guidance.

## Key Files Reference

| File | Purpose |
|------|---------|
| [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) | Full skill specification including time estimate rules (section 6, lines 82-88) |
| [`.opencode/command/i-have-adhd.md`](https://github.com/ayghri/i-have-adhd/blob/main/.opencode/command/i-have-adhd.md) | OpenCode CLI documentation for invoking the skill |
| [`README.md`](https://github.com/ayghri/i-have-adhd/blob/main/README.md) | Repository overview and high-level usage guidance |

## Summary

- The **i-have-adhd skill time estimate format** requires explicit units: minutes, hours, or days with optional conditional qualifiers.
- The rule lives in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) at lines 82-88 under section 6.
- Vague terms like "some work" or "later" violate the specification and should never appear.
- Inline step estimates use bold formatting: `– **15 minutes**.`
- This format reduces decision friction specifically designed for ADHD-focused task management.

## Frequently Asked Questions

### What happens if I use a vague time estimate with the i-have-adhd skill?

The skill specification in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) explicitly flags vague estimates as non-compliant. While the repository doesn't contain automated enforcement code, following the guidelines ensures consistent, actionable output that serves the skill's intended audience.

### Can I use weeks or months as units in i-have-adhd time estimates?

The specification emphasizes concrete, actionable timeframes. While not explicitly forbidden, "weeks" or "months" fall outside the practical scope this skill targets. Stick to **minutes, hours, or days** for estimates that support immediate task initiation.

### Where else is the i-have-adhd skill documented besides SKILL.md?

Additional documentation appears in [`.opencode/command/i-have-adhd.md`](https://github.com/ayghri/i-have-adhd/blob/main/.opencode/command/i-have-adhd.md) for CLI invocation and [`README.md`](https://github.com/ayghri/i-have-adhd/blob/main/README.md) for repository overview. The time estimate rule itself is only fully detailed in the main skill specification file.

### Is the i-have-adhd skill format compatible with other productivity systems?

Yes. The concrete unit format translates directly into time-blocking methods, Pomodoro techniques, or calendar scheduling. The explicit nature of "25 minutes" or "2 hours" makes it interoperable with virtually any external productivity tool.