I-HAVE-ADHD Skill + Claude,Codex,Deepseek: YOU'RE MISSING OUT without THIS SKILL!
This video demystifies the viral "I Have ADHD" Claude Code skill, a single MIT-licensed skill.md file that forces AI coding assistants to answer action-first, numbered, and filler-free instead of burying commands in paragraphs of preamble.
AICodeKing7 minTranscript found
Quick learning frame
Read this before watching.
Coding-agent workflow is the loop of inspect, route, plan, edit, verify, summarize, and decide what should be automated next.
New playlist item from AICodeKing; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Skill you build: The ability to install, evaluate, and customize a response-formatting skill so an AI coding agent leads with actions and progress state instead of verbose explanations.
Watch for the shift from claim to mechanism. The learning value is the point where the transcript reveals a repeatable action, tool boundary, context move, review habit, or artifact.
Concept diagram
Where this video fits.
01Inspect context
02Route tool
03Plan work
04Edit safely
05Verify behavior
06Report next step
Deep lesson
Turn this video into working knowledge.
1,246 cleaned transcript words reviewed across 367 timed caption segments.
Thesis
I-HAVE-ADHD Skill + Claude,Codex,Deepseek: YOU'RE MISSING OUT without THIS SKILL! teaches a practical coding-agent workflow move: This video demystifies the viral "I Have ADHD" Claude Code skill, a single MIT-licensed skill.md file that forces AI coding assistants to answer action-first, numbered, and filler-free instead of burying commands in paragraphs of preamble.
The goal is not to remember the video. The goal is to extract the operating principle, tie it to timestamped evidence, test how far the claim transfers, and make something reusable.
0:20
10 rules, one file
“file. Now, before you ask, no, you don't need an actual ADHD diagnosis to use this. The whole point of this plugin is that it fixes something that annoys literally everyone who uses AI coding assistants, and that's...”
The skill, made by developer Igri and loosely inspired by an ADHD toolkit book, encodes 10 rules such as leading with the action, numbering every multi-step task as single bounded actions, ending each response with one concrete next action under two minutes, and suppressing tangents until the main issue is resolved. Write out your own top-3 rules you'd want an AI assistant to follow based on your biggest complaint about its current responses.
3:36
State restating and caps
“genuinely ambiguous, it'll ask one clarifying question instead of guessing. So, it's not just blindly tur, which I appreciate. Now, let's install it and see it in action. The installation is pretty simple. Run claude plug-in install I...”
The skill has the agent restate progress on every turn (e.g. "step three of five done"), give specific time estimates instead of vague ones, report errors matter-of-factly with cause and fix, and cap lists at five items with no closing pleasantries like "let me know if this helps." Take a recent verbose AI response you received and rewrite it manually following the restate-progress and five-item-cap rules to feel the difference.
5:03
Install and demo it
“file, you can fork the repo, edit the file at skills/avadh/skill.md, and change whatever you want. Maybe you want lists capped at three items instead of five, or you want it even more aggressive with the brevity. You...”
Installing is one command, claude plugin install i-have-adhd@i-have-adhd, then /avadhd activates it inside Claude Code; a live side-by-side on adding JWT authentication showed the unskilled response burying commands in explanation while the skilled response opened with the install command, four numbered steps with exact file/line edits, and a 20-minute estimate. Install the skill yourself and run the same before/after test on a task you actually need done this week.
01
Inspect context
Start with this video's job: This video demystifies the viral "I Have ADHD" Claude Code skill, a single MIT-licensed skill.md file that forces AI coding assistants to answer action-first, numbered, and filler-free instead of burying commands in paragraphs of preamble. Treat "Inspect context" as the outcome you are trying to make visible, not a topic label. Anchor it to 0:20, where the video says: “file. Now, before you ask, no, you don't need an actual ADHD diagnosis to use this. The whole point of this plugin is that it fixes something that annoys literally everyone who uses AI coding assistants, and that's...”
02
Route tool
Use "Route tool" to locate the part of the coding-agent workflow mechanism the video is demonstrating. Ask what changes in your real setup if this claim is true. Anchor it to 3:36, where the video says: “genuinely ambiguous, it'll ask one clarifying question instead of guessing. So, it's not just blindly tur, which I appreciate. Now, let's install it and see it in action. The installation is pretty simple. Run claude plug-in install I...”
03
Plan work
Turn "Plan work" into the reusable artifact for this lesson: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal. This is where watching becomes something you can inspect and reuse.
04
Edit safely
Use "Edit safely" as the application surface. Decide whether the idea touches a browser flow, a local file, a model choice, a source document, a UI, or a review step.
05
Verify behavior
Use "Verify behavior" to prove the lesson. The evidence should connect back to the video title, transcript anchors, and a concrete output, not a generic best-practice claim.
06
Report next step
Use "Report next step" to carry the idea forward: save the prompt, checklist, diagram, or operating rule that would make the next agent run better.
Example
Source-backed artifact packet
Convert the video into a scoped artifact request that includes the transcript claim, mechanism, acceptance criteria, and proof. The output should be a coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal..
Example
Coding-agent workflow proof brief
Separate what the speaker claims, what the demo actually proves, and what still needs outside verification before you adopt the coding-agent workflow pattern.
Example
Teach-back module
Transform the lesson into a definition, a Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step diagram, one misconception, one practice exercise, and a check-for-understanding question.
Do not learn it wrong
Treating the title as the lesson without checking what the transcript actually says.
choosing tools by hype
losing context across agents
letting parallel sessions become invisible
Letting the lesson drift into generic Codex vs Claude comparison.
Letting the lesson drift into feature lists without task routing.
Letting the lesson drift into claims that ignore limits or recovery.
Do not count this as learned until these are true.
01
State the transcript-backed claim in your own words: This video demystifies the viral "I Have ADHD" Claude Code skill, a single MIT-licensed skill.md file that forces AI coding assistants to answer action-first, numbered, and filler-free instead of burying commands in paragraphs of preamble.
02
Explain the practical stakes without hype: New playlist item from AICodeKing; queued for transcript-backed review, topic mapping, and a practical learning artifact.
03
Map the idea onto the Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step sequence and name the weakest link.
04
Produce the artifact and include the evidence that proves it: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
Put it into practice
Give this grounded prompt to Codex or Claude after watching.
You are helping me turn one specific YouTube video into real, durable learning.
Source video:
- Title: I-HAVE-ADHD Skill + Claude,Codex,Deepseek: YOU'RE MISSING OUT without THIS SKILL!
- URL: https://www.youtube.com/watch?v=EpU0Cj4jlVg
- Topic: Creative Automation
- My current learning frame: Install the I Have ADHD skill in Claude Code, ask it the same real coding question with the skill off and then on, and compare how much faster you can locate the actionable command in each response.
- Why this matters: New playlist item from AICodeKing; queued for transcript-backed review, topic mapping, and a practical learning artifact.
Transcript anchors from this exact video:
- 0:20 / Evidence 1: "file. Now, before you ask, no, you don't need an actual ADHD diagnosis to use this. The whole point of this plugin is that it fixes something that annoys literally everyone who uses AI coding assistants, and that's..."
- 2:00 / Evidence 2: "quickly run you through the main rules because this is where it gets good. First, the AI has to lead with the action. So instead of explaining why authentication is complex, it just tells you to run the..."
- 3:36 / Evidence 3: "genuinely ambiguous, it'll ask one clarifying question instead of guessing. So, it's not just blindly tur, which I appreciate. Now, let's install it and see it in action. The installation is pretty simple. Run claude plug-in install I..."
- 5:03 / Evidence 4: "file, you can fork the repo, edit the file at skills/avadh/skill.md, and change whatever you want. Maybe you want lists capped at three items instead of five, or you want it even more aggressive with the brevity. You..."
Video-aware target:
- Prompt lane: Coding-agent workflow
- Mechanism to extract: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review.
- Artifact to produce: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
- Artifact must include: task class; agent/tool choice; context packet; verification step; handoff/recovery rule
Your task:
1. Use the transcript anchors above as the primary source packet. If you add outside context, label it clearly as outside context and keep it secondary.
2. Create a source-check table with columns: timestamp, claim, transcript support, what the demo proves, confidence, and what still needs verification.
3. Extract the actual teachable mechanism from the video: Find the workflow rule that explains when and how to use Codex, Claude Code, browser control, dashboards, or manual review. Do not invent claims that are not supported by the title, lesson frame, or transcript anchors.
4. Build a reusable learning artifact: A coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal.
5. Include:
- a plain-English definition of the core idea
- a diagram or structured model using this sequence: Inspect context -> Route tool -> Plan work -> Edit safely -> Verify behavior -> Report next step
- answers to these source questions: What workflow pain is being solved? | What exact coordination mechanism is shown? | What evidence proves it changes the work?
- 3 concrete examples that apply the video idea to real agentic work, such as rate-limit routing; browser verification after a UI edit; long-running /goal session review
- 2 failure modes the video helps prevent, chosen from the transcript evidence and these likely risks: choosing tools by hype; losing context across agents; letting parallel sessions become invisible
- a checklist for the next real workflow, focused on: routing decision, context portability, verification, handoff summary
- one practical exercise with a clear done signal: Route three recent tasks across Codex, Claude, browser checks, and manual review with a reason for each.
6. Add a "learning transfer" section: what changes in my workflow tomorrow if I actually learned this?
7. Add a "source check" section that cites which transcript anchor supports each major takeaway.
Quality bar:
- Make this specific to "I-HAVE-ADHD Skill + Claude,Codex,Deepseek: YOU'RE MISSING OUT without THIS SKILL!", not a generic Creative Automation essay.
- Each workflow rule must point to a timestamped claim or demo moment, then state what remains unproven.
- Prefer operational examples, failure modes, and reusable artifacts over broad definitions.
- Call out uncertainty instead of smoothing over weak evidence.
- Avoid these generic drifts: generic Codex vs Claude comparison; feature lists without task routing; claims that ignore limits or recovery.
- If evidence is weak or missing, stop and say what transcript segment or timestamp needs review instead of guessing.
- Finish with a concise artifact I could paste into my learning app.
Misconceptions
What to stop believing.
Creative AI removes the need for taste.
It increases the need for taste because output volume explodes.
The best prompt is enough.
References, critique, iteration, and post-production matter just as much.
Practice studio
Learning only counts when you make something.
01
Transcript evidence map
Separate what the video actually says from what you already believe about the topic.
3 source-backed takeaways with timestamps, confidence, and a transfer note.02
One useful artifact
Apply the video to a real workflow and produce a coding-agent routing and execution matrix with context needed, tool choice, verification, and done signal..
A reusable artifact with a done signal and one verification step.03
Coding-agent workflow teach-back card
Explain the coding-agent workflow mechanism to someone who has not watched the video yet.
A 90-second explanation, one diagram, one example, and one misconception to avoid.
Recall check
Answer first, then reveal — without rewatching.
What is the I Have ADHD skill and what problem is it trying to fix in AI coding assistants?
How does the skill keep a learner oriented during a long multi-step agentic session?
In the JWT authentication demo, what was the key difference between the response with the skill off versus on?
Source shelf
Use the video as a doorway, then verify with primary sources.
