# How the i-have-adhd Skill Handles "Explain" and "Walk Me Through" Requests

> Discover how the i-have-adhd skill explains complex topics and walks you through tasks. It uses Markdown headers for clear, skimmable content, removing unnecessary preamble for efficient learning.

- Repository: [Ayoub Ghriss/i-have-adhd](https://github.com/ayghri/i-have-adhd)
- Tags: how-to-guide
- Published: 2026-08-21

---

**The i-have-adhd skill processes "explain" or "walk me through" requests by generating comprehensive, uninterrupted explanations that eliminate conversational preambles and closing statements, instead utilizing hierarchical Markdown headers to organize content of arbitrary length for optimal skimming.**

The `i-have-adhd` repository (`ayghri/i-have-adhd`) implements a specialized response protocol for educational prompts. When users trigger explanation requests, the skill activates a distinct formatting mode defined in its canonical skill definition to minimize cognitive overhead and support sustained attention patterns.

## The Core Protocol in SKILL.md

According to the authoritative skill definition in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) (line 121), the skill enforces a strict formatting rule for explanation requests:

> "User asks to 'explain' or 'walk me through.' Explain fully. Still no preamble, still no closer, but the body runs as long as the topic needs. Add headers so the reader can skim back."

This specification is reinforced in [`INSTALL.md`](https://github.com/ayghri/i-have-adhd/blob/main/INSTALL.md) (line 53), where the installation guide restates the requirement for developers to **explain fully** when such request patterns are detected.

## Structural Requirements for Explanation Mode

### Elimination of Conversational Framing

Unlike standard conversational responses, the skill **omits social framing**. Responses do not include introductory phrases such as "Sure, here's..." or closing statements like "Hope that helps!" This reduction eliminates extraneous cognitive processing, allowing the reader to engage immediately with the substantive content.

### Hierarchical Header Organization

To accommodate the **arbitrary length** of comprehensive explanations, the skill injects Markdown headers (`##` and `###`) to create clear document architecture. These hierarchical markers enable users to:
- Navigate lengthy content efficiently
- Return to specific sections without re-reading
- Maintain spatial awareness within complex topics

### Unrestricted Content Length

The protocol explicitly allows the response body to **run as long as the topic needs**, constrained only by inherent model token limits. This supports deep, thorough explanations without artificial truncation or summarization that might compromise understanding.

## Practical Response Examples

The following examples demonstrate the formatting standards applied to "explain" and "walk me through" requests:

```markdown
**User Prompt**  
> Explain how the Pomodoro Technique works.

**Skill Response**  

## Overview  

The Pomodoro Technique is a time‑management method that breaks work into intervals...

## The Basic Cycle  

1. **Set a timer for 25 minutes** – this interval is called a *Pomodoro*.  
2. **Work on a single task** until the timer rings.  
3. **Take a short break** (5 minutes).  
4. **After four Pomodoros**, take a longer break (15–30 minutes).

## Benefits  

- Improves focus by limiting distractions.  
- Provides regular rest, reducing mental fatigue...

*(No introductory “Sure, here’s…” and no closing “Hope that helps!”)*

```

```markdown
**User Prompt**  
> Walk me through setting up a GitHub Actions workflow for CI.

**Skill Response**  

## Prerequisites  

- A GitHub repository.  
- Permissions to create workflow files in `.github/workflows`.

## Step‑by‑Step Guide  

### 1️⃣ Create the workflow file  

```yaml
name: CI
on: [push, pull_request]
jobs:
  build:
    runs-on: ubuntu‑latest
    steps:
      - uses: actions/checkout@v3
      - name: Install dependencies
        run: npm ci
      - name: Run tests
        run: npm test

```  

### 2️⃣ Commit the file  

```bash
git add .github/workflows/ci.yml
git commit -m "Add CI workflow"
git push

```  

*(Response starts directly with the explanation and ends after the last step.)*

```

## Summary

- **Primary Rule**: Defined in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) (line 121), the skill detects "explain" or "walk me through" requests and switches to comprehensive explanation mode
- **Format Constraints**: Responses exclude conversational preambles and closing statements to reduce cognitive load
- **Structural Elements**: Hierarchical Markdown headers (`##`, `###`) organize content for non-linear reading and easy navigation
- **Length Policy**: Content extends as long as necessary to fully cover the topic, limited only by model token capacity
- **Documentation**: The protocol is documented in both [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md) and [`INSTALL.md`](https://github.com/ayghri/i-have-adhd/blob/main/INSTALL.md) (line 53) for implementation reference

## Frequently Asked Questions

### Where is the explain request handling defined in the i-have-adhd source code?

The handling logic is defined in [`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md) at line 121, which contains the canonical rule for processing "explain" or "walk me through" prompts. This specification is reiterated in [`INSTALL.md`](https://github.com/ayghri/i-have-adhd/blob/main/INSTALL.md) at line 53 to ensure consistent implementation across deployments.

### Why does the i-have-adhd skill remove preambles for explain requests?

The skill eliminates introductory and closing social formulas to minimize cognitive overhead for users with ADHD. By removing phrases like "Sure, here's..." and "Hope that helps!", the response delivers immediate value without requiring the reader to process polite conversational conventions before accessing the substantive information.

### How does the skill organize long explanations?

The skill organizes lengthy content using hierarchical Markdown headers (`##` for sections, `###` for subsections). This header structure creates a scannable document architecture that allows readers to jump between sections, backtrack efficiently, and maintain orientation within complex, arbitrarily long explanations.

### Does the skill limit the length of explanations?

No. According to the source code in [`SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/SKILL.md), the body of the response **runs as long as the topic needs**, constrained only by the inherent token limits of the underlying language model. This policy ensures comprehensive coverage without artificial summarization or truncation.