# How the i-have-adhd Skill Handles "Explain" or "Walk Me Through" Requests > Discover how the i-have-adhd skill handles explain or walk me through requests with detailed, structured responses bypassing its usual brevity. - Repository: [Ayoub Ghriss/i-have-adhd](https://github.com/ayghri/i-have-adhd) - Tags: how-to-guide - Published: 2026-08-27 --- **The i-have-adhd skill makes a deliberate exception to its brevity-first design when users explicitly ask for an explanation or step-by-step walk-through, allowing longer, fully structured responses without preamble or closing pleasantries.** The **i-have-adhd** skill is designed to keep output concise and action-oriented for readers with ADHD who benefit from immediate, digestible guidance. However, as documented in the source code, it recognizes that some requests inherently require depth. When a user triggers the explanation mode, the skill adapts its constraints while maintaining ADHD-friendly structural principles. ## The Core Rule in SKILL.md The canonical rule governing this behavior 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. The directive states: > "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 rule creates a controlled expansion of response length without abandoning the skill's accessibility principles. ## What Changes When Explanation Mode Activates The skill applies four specific adaptations when handling "explain" or "walk me through" requests: - **Brevity constraints are suspended** — The body can extend as long as necessary to cover the topic completely - **Preamble and closer remain prohibited** — No "Sure, I'd be happy to explain..." introductions or "Let me know if you need anything else" conclusions - **Structural headers are required** — Markdown headings (H2, H3) must break content into skimmable sections - **ADHD-friendly fundamentals persist** — Direct language, clear actionable items, and elimination of tangents ## Practical Response Structure According to **[`AGENTS.md`](https://github.com/ayghri/i-have-adhd/blob/main/AGENTS.md)** and the skill implementation, the skill maps these rule files to runtime adapters that enforce the output format. The generated responses follow a predictable pattern: ### Starting Point Responses begin immediately with the first header and content — no acknowledgment of the request itself. ### Body Organization Content flows through logically sequenced sections with descriptive headers. For step-by-step instructions, numbered lists appear within header-defined phases. ### Termination Responses end after the final substantive point — no transition to a closing question or offer of further assistance. ## Code Examples from the Skill The following patterns demonstrate how the skill generates output when explanation mode activates. ### Example: Technical Explanation **User input:** ```text Explain how OAuth 2.0 works. ``` **Skill output structure:** ```markdown ## OAuth 2.0 Overview OAuth 2.0 is an authorization framework that allows a user to grant... ## Grant Types 1. **Authorization Code** — ... 2. **Implicit** — ... ## Token Flow Step 1: The client redirects the user to the authorization server... Step 2: The user authenticates and approves... ``` ### Example: Step-by-Step Walk-Through **User input:** ```text Walk me through rebasing a feature branch onto main. ``` **Skill output structure:** ```markdown ## Rebase Workflow 1. Checkout the feature branch: `git checkout feature-branch` 2. Pull the latest main: `git fetch origin && git rebase origin/main` 3. Resolve any conflicts... 4. Finish the rebase: `git rebase --continue` 5. Verify the history: `git log --oneline` ``` ## Key Implementation Files - **[`skills/i-have-adhd/SKILL.md`](https://github.com/ayghri/i-have-adhd/blob/main/skills/i-have-adhd/SKILL.md)** — Contains the full rule set including the "explain / walk-through" exception at line 121 - **[`AGENTS.md`](https://github.com/ayghri/i-have-adhd/blob/main/AGENTS.md)** — Maps skill definitions to runtime adapters and loading guidance ## Summary - The i-have-adhd skill normally enforces brevity but expands output scope for explicit explanation requests - Rule 21 in **SKILL.md** mandates full explanations with headers but maintains the no-preamble, no-closer policy - Responses use Markdown headings to preserve skimmability for ADHD readers despite increased length - The skill loads through adapters defined in **AGENTS.md** with rules parsed from the canonical skill definition ## Frequently Asked Questions ### What exact phrases trigger the explanation mode? The skill responds to the specific phrases "explain" or "walk me through" as documented in **SKILL.md**. These keywords signal that the user requires comprehensive coverage rather than concise guidance, causing the skill to suspend its standard length constraints while keeping structural safeguards intact. ### Why keep the no-preamble rule even during long explanations? The no-preamble policy addresses cognitive friction for ADHD readers. Introductory filler like "Here's an explanation of..." adds processing overhead before value delivery. By starting immediately with substantive content, the skill respects the reader's attention and reduces the barrier to engagement. ### How does the skill use headers differently in explanation mode? While standard responses may use minimal or no headers, explanation mode requires them per rule 21. Headers function as cognitive bookmarks, enabling readers to scan backward efficiently if they lose their place or need to reference earlier sections. This compensates for the increased cognitive load of longer content. ### Does explanation mode allow tangents or conversational asides? No. The skill's core directive against unnecessary filler persists. The expanded length serves only the topic's inherent complexity, not digressive elaboration. Every section must advance understanding of the requested explanation or walk-through.