The ADHD Developer Tool Stack: What Actually Replaces Executive Function

Every unplanned context switch costs a developer real time to recover from, and an ADHD brain pays that cost more often and more expensively than a neurotypical one. Multiply that by every Slack ping, every “quick question,” every time you look up from a rabbit hole and realize you’ve lost the afternoon, and the tax adds up to entire days of work that never gets billed, shipped, or even remembered as having happened.

The standard advice for this is willpower: focus harder, block your calendar, use a to-do list. None of that addresses the actual mechanism. ADHD is not a focus deficit, it’s an executive-function deficit: working memory, time perception, task initiation, and self-monitoring all run at reduced reliability, and no amount of discipline restores a function that isn’t there to summon. What works instead is replacing each broken function with something external that does the same job, the same principle behind building environmental scaffolding for remote work in general.

This post is for developers who recognize the pattern: you know the engineering, the code is not the hard part, but something between “know what to do” and “actually doing it” keeps failing in ways that look like laziness from the outside and feel like a locked door from the inside. The tools below don’t teach discipline. They sit in the specific spot where the executive function used to be and do that job instead.

This is the tool stack I actually use for that, grouped by which specific failure mode each tool targets, not by category. The 5-step Claude Code workflow covers the day-to-day sequence this stack supports. This post is the tool-by-tool breakdown.

Externalize Working Memory: Claude Code + CLAUDE.md

The failure mode: you close a task mid-thought, come back later, and your brain has quietly deleted the mental model of what you were doing. You don’t remember you already fixed something, so you fix it again.

That’s not a hypothetical. On a live trading bot rebuild, after closing 14 tabs mid-refactor, I reopened a file I had already fixed that morning, the entire afternoon’s context gone between the fix and the reopen. The same failure shows up project-wide: I once literally re-fixed a bug I had closed four hours earlier, because nothing external had recorded that it was already done.

Claude Code with a CLAUDE.md file at the project root fixes this by giving you a persistent place to write project context, brain-specific rules, and a running checkpoint of what you last did and what’s next. Claude reads it automatically at the start of every session, so the reconstruction that used to take an hour of staring at code you don’t remember writing takes minutes of reading a file that tells you where you left off.

Usage note: the file only works if you actually update the checkpoint before closing a session. Skip that step enough times and the next session starts cold anyway, the tool doesn’t fix the discipline gap on its own, it just gives the discipline somewhere cheap to land.

Body Doubling: Focusmate

The failure mode: tasks with no social visibility, the ones nobody is watching you do, get avoided indefinitely. Documentation, admin, anything without an audience.

Focusmate puts a real person on video with you for a scheduled 50-minute session: you both say what you’re working on, work silently, then check back in. It works because it activates the same social-accountability mechanism an office provides passively, except you have to schedule it instead of getting it for free by walking into a building.

I’ve used it specifically to get through tax returns, documentation, and every other task that normally gets avoided indefinitely. It doesn’t make boring work interesting. It makes the avoidance cost more than the task, because now a real person is expecting you to show up.

Time Blindness: Passive Time Tracking

The failure mode: four hours feel like forty minutes, and you have no internal signal telling you otherwise. Deadlines get missed not from procrastination but from a genuine inability to perceive duration.

The fix is a tool that tracks time without requiring you to remember to start it, because remembering to start a timer is itself an executive-function task and it’s the first thing that gets dropped. Toggl gives you a lightweight always-on tracker you can tag by project after the fact instead of before. RescueTime runs entirely in the background and reconstructs where your day actually went, which matters more for ADHD than for most people, because the gap between where you think your time went and where it actually went is usually the whole problem.

Neither tool fixes time blindness. What they do is turn an invisible problem into a visible one you can act on after the fact, which is the only point where an ADHD brain has any leverage over it. The same logic behind 90-minute alarms and scheduled video calls as time anchors applies here: the goal isn’t perfect time management, it’s an external signal loud enough to overrule a brain that has no internal one.

Reduce Friction: Launchers and Automation

The failure mode: task initiation paralysis doesn’t need a hard task to trigger it, it needs friction. An extra click, an extra app switch, a form that takes ninety seconds to fill out, any of these is enough to stall a brain that runs on activation energy it doesn’t reliably generate.

Raycast collapses app-switching, file search, and quick actions into one keyboard-driven launcher, so the friction of getting from “I need to do X” to actually doing X drops from several clicks to a few keystrokes. For repetitive multi-step tasks that would otherwise require you to hold a sequence in working memory every time, n8n lets you build the sequence once as a visual workflow and never re-derive the steps again, whether that’s a data pipeline or an AI agent orchestration chain.

Neither tool addresses a big problem. That’s the point. ADHD task-initiation failures are usually death by a thousand small frictions, not one large obstacle, and the fix scales the same way.

What This Doesn’t Fix

None of these six tools address ADHD itself. They address the specific external gaps ADHD leaves behind: a memory system that doesn’t reliably persist across interruptions, a time sense that doesn’t reliably track duration, a social-accountability circuit that needs another person present to activate, and an initiation threshold that friction pushes out of reach. Match the tool to the failure mode costing you the most time this week, not to what looks impressive as a stack.

Adopting all six at once usually backfires. Each one adds a habit you have to remember to run, and remembering to run habits is exactly the function that’s unreliable in the first place. Start with the single tool that maps to your worst failure mode, let it become automatic, then add the next one. A stack you actually use beats a complete one you abandon in week two.

If you want the deeper system this stack plugs into, the 5-step Claude Code workflow covers the day-to-day sequence these tools support, and the ADHD Engineer’s Productivity System packages the non-software side, energy-based task management and brain-dump capture, into a ready-to-use template.