📋 Free Download · 47 Items
The AI Fatigue Recovery Checklist
47 evidence-based signs, daily boundaries, and recovery prompts — used by 2,000+ engineers to track and reverse AI fatigue. Print it. Use it. Share it.
47Checklist items
5Review sections
2,000+Engineers using it
Your checklist progress0 / 47 checked
Section 1 — Recognizing AI Fatigue
Check any that applied to your last 2 weeks. Not a judgment — just noticing.
I've shipped code I couldn't explain in detail to a colleague Awareness
Sunday dread that wasn't there 6 months ago Signal
I open AI tools before I've even thought through a problem myself Pattern
Productivity feels high but confidence in my own skills feels low Signal
Can't recall the last time I solved a hard problem entirely on my own and felt good about it Pattern
I feel busier but less satisfied at the end of the day Signal
I avoid starting tasks without AI assistance — even small ones Pattern
When asked how I built something, my instinct is to show the prompt, not the solution Pattern
I feel guilty or restless when I work without AI for more than 30 minutes Signal
I've stopped starting side projects because AI makes it "too easy" — and they never feel like mine Pattern
Section 2 — The Weekly Recovery Review
A structured 10-minute review to do every Sunday evening. Track patterns over 4+ weeks.
This week, I had at least 3 sessions where I built something with minimal AI help Practice
I protected at least one 90-minute block of uninterrupted deep work Practice
I used AI to teach myself something, not just to produce output Practice
I noticed at least one moment where I understood something more deeply than the AI explanation Practice
I can articulate at least one thing I built or solved this week that I actually own Practice
My Sunday evening dread was noticeably lower than the previous week Signal
I told at least one colleague something I figured out entirely on my own Practice
I spent at least 30 minutes doing something with a screen, but not AI (walk, reading, drawing) Rest
I felt genuine satisfaction when something I built actually worked — not just "shipped" Practice
My confidence this week felt grounded in what I actually know — not what AI can do for me Signal
Section 3 — Daily Boundaries
Pick 3–5 that you can actually commit to this week. Start small. Consistency beats ambition.
First 30 minutes of the workday: no AI tools Boundary
No AI for first problem-solving attempt — struggle with it first Boundary
One "no-AI block" per day: 60 minutes where I build without assistance Boundary
End of day: before I close my laptop, I write 2-3 sentences about what I actually learned today Reflection
AI output only after I've formed my own initial hypothesis or approach Boundary
No AI on Sunday evenings — one day without the tool Boundary
When debugging: try 20 minutes alone before opening AI Boundary
Every AI-assisted build ends with an explanation: why this approach, not another Reflection
No AI tabs open during meetings — presence over productivity theater Boundary
Weekly: build one small thing from scratch without any AI (CSS is fine, prompts are not) Practice
Section 4 — Signs You Need a Reset
Check any that are frequent or persistent. More than 5 checked = you're in the compounding zone. Take action.
I can't explain the last 3 features I shipped in any detail Danger
Sunday evenings are consistently dread-filled with no project interest Danger
I've lost the ability to start anything without AI assistance Danger
My sleep is consistently poor — I wake up tired or can't fall asleep easily Danger
I feel anxious if I haven't checked AI tools for more than a few hours Danger
My colleagues have started asking me how things work and I have to ask AI to check Danger
I've stopped reading technical content because AI "covers it" Warning
I can't tell the difference between what I know and what AI knows Warning
My job satisfaction has dropped significantly even though my output is higher Warning
I've had thoughts along the lines of "maybe I'm not cut out for this anymore" Warning
Section 5 — Team & Manager Conversation Guide
For engineering managers and tech leads. Use in 1:1s, retros, or team conversations.
Our team has explicit norms around when AI assistance is expected vs. optional Team Norm
I regularly see team members solving problems without AI in our team channels Team Culture
Our team celebrates ships that came from genuine understanding, not just output Team Culture
I've noticed at least one team member showing signs of skill atrophy or disengagement Signal
We have at least one "no-AI session" or deep work block per week as a team norm Team Norm
I can name at least one project or feature where the IC genuinely owns the technical approach Team Culture
Our team has talked openly about AI fatigue as a real thing, not a weakness Team Norm
I've pushed back on a timeline at least once this quarter to protect learning time Signal
At least one person on my team has said something like "I don't feel like I'm learning anymore" Danger
Our team velocity metric is going up but our average engineer confidence is going down Danger
[data-theme="light"] .print-section p {color:var(--text-muted)}
Opens your browser's print dialog. Save as PDF to keep a copy.
Frequently Asked Questions
Is this checklist really free? ▾
Yes. 100% free. No email required, no upsell, no premium version. The Clearing is a free resource built for engineers by engineers.
How is this different from the AI Fatigue Quiz? ▾
The quiz tells you where you stand right now — a one-time diagnostic. This checklist is a structured weekly review ritual. Use it every Sunday evening to track your patterns over 4+ weeks.
I'm already burned out. Is this too much? ▾
Start with Section 1 only. You don't need to complete the whole thing. Even noticing 2-3 items that land for you is useful. Recovery starts with recognition.
Can managers use this with their teams? ▾
Yes. Section 5 is specifically written for manager-led 1:1 conversations. The team checklist items are designed to be discussed, not used as a performance evaluation.
Continue Exploring
Tools and guides to go deeper with your recovery.
AI Fatigue Quiz
Find out which tier of AI fatigue you're in and what to do about it.
Recovery Guide
7-phase structured recovery plan for AI-fatigued engineers.
Daily Boundaries
12 daily habits for engineers to maintain healthy AI boundaries.
Skill Atrophy
The science of why AI slowly erodes your coding skills.
30-Day AI Detox
A structured 30-day reset plan for deep recovery.
Daily Check-in
30 hand-crafted daily reflection questions to build self-awareness.