Planning and Task Management skill 10 of 13
Focus and Deep Work SKILL.md
The Focus and Deep Work skill makes Claude, Codex or another AI agent help you protect and use focused time. It chooses the work that deserves deep focus, picks a focus pattern that fits your role, books and defends calendar blocks, sets team norms and an urgent route, reduces interruptions at the source, builds a start ritual, batches messages and reviews focus hours weekly.
focus-deep-work/SKILL.md, version 1.0.0, 1,504 words.
By Afeez Adebayo, Marketing, SEO & Growth Expert with 10+ years of experience.
Created 10 October 2026. Updated 10 October 2026. Free to use under CC BY 4.0.
Knowledge work rewards long stretches of concentration, yet most workdays are cut into fragments by meetings, messages and notifications. Cal Newport's book Deep Work argues that the ability to focus without distraction on hard tasks is increasingly rare and valuable. [Reference, Deep Work] Research by Gloria Mark and colleagues found people interrupted during tasks compensated by working faster, but reported more stress and frustration. [Research, Mark et al. 2008] Sophie Leroy described "attention residue": after switching tasks, part of the mind stays on the previous one, lowering performance on the next. [Research, Leroy 2009]
This skill helps people protect and use focused time: choosing the work that deserves it, scheduling focus blocks, reducing interruptions, preparing a focus routine, handling messages without losing the thread, and reviewing what worked. It balances focus with real job demands such as support, management and collaboration.
Operating principles
- Focus is scheduled, not found. Book it like a meeting before the week fills.
- One task per block. Decide the task before the block starts.
- Remove triggers, not just resist them. Notifications off, phone away, tabs closed.
- Batch the shallow work. Email and chat in set windows, not all day.
- Fit the role. A support lead and a writer need different focus patterns.
Focus patterns
| Pattern | How it works | Fits |
|---|---|---|
| Daily focus block | 90 to 120 minutes at the same time each day | Most knowledge workers |
| Focus days | One or two meeting-free days a week | Makers, writers, engineers |
| Sprints | 25 to 50 minutes of focus, 5 to 10 minutes break, repeated | Interruptible roles, getting started |
| Seasonal | Weeks of intense focus between busy periods | Researchers, founders, writers |
| Team focus hours | Whole team pauses meetings and chat for set hours | Teams sharing calendars |
When to use, and when not to
Use it when important work keeps getting pushed aside, the day is fragmented, notifications dominate, a big piece of thinking work is due, or a team wants protected focus time.
Don't use it to treat attention difficulties that may need assessment; suggest a qualified professional while still offering practical strategies. Don't use it to ignore real responsibilities such as on-call duties or customer commitments.
Inputs
- The important work that needs focus.
- Calendar and typical meeting pattern.
- Main sources of interruption (chat, email, phone, colleagues, home).
- Energy pattern: when the person thinks best.
- Role demands: response expectations, on-call, management.
Raw SKILL.md file
This is the exact file agents read, including the credit header and licence notice. Save it as focus-deep-work/SKILL.md.
--- name: focus-deep-work description: "Protect and use focused time: choosing work that deserves deep focus, focus patterns from daily blocks to focus days and sprints, booking and defending calendar blocks, team norms and urgent routes, interruption reduction, a start ritual, handling attention residue, message batching and weekly focus-hour reviews. Use whenever someone cannot focus, has a fragmented day, keeps getting interrupted, needs deep work time for writing, analysis or coding, wants fewer notifications or wants team focus hours." license: CC-BY-4.0 metadata: author: Afeez Adebayo author_url: https://afeezadebayo.com author_linkedin: https://www.linkedin.com/in/afeez-adebayo/ author_x: https://x.com/za_icon source: https://afeezadebayo.com/skills-md/productivity/planning-tasks/focus-deep-work/ category: productivity subcategory: planning-tasks version: "1.0.0" created: "2026-10-10" updated: "2026-10-13" --- # Focus and Deep Work Knowledge work rewards long stretches of concentration, yet most workdays are cut into fragments by meetings, messages and notifications. Cal Newport's book Deep Work argues that the ability to focus without distraction on hard tasks is increasingly rare and valuable. [Reference, Deep Work] Research by Gloria Mark and colleagues found people interrupted during tasks compensated by working faster, but reported more stress and frustration. [Research, Mark et al. 2008] Sophie Leroy described "attention residue": after switching tasks, part of the mind stays on the previous one, lowering performance on the next. [Research, Leroy 2009] This skill helps people protect and use focused time: choosing the work that deserves it, scheduling focus blocks, reducing interruptions, preparing a focus routine, handling messages without losing the thread, and reviewing what worked. It balances focus with real job demands such as support, management and collaboration. ## Operating principles 1. **Focus is scheduled, not found.** Book it like a meeting before the week fills. 2. **One task per block.** Decide the task before the block starts. 3. **Remove triggers, not just resist them.** Notifications off, phone away, tabs closed. 4. **Batch the shallow work.** Email and chat in set windows, not all day. 5. **Fit the role.** A support lead and a writer need different focus patterns. ## Focus patterns | Pattern | How it works | Fits | |---|---|---| | Daily focus block | 90 to 120 minutes at the same time each day | Most knowledge workers | | Focus days | One or two meeting-free days a week | Makers, writers, engineers | | Sprints | 25 to 50 minutes of focus, 5 to 10 minutes break, repeated | Interruptible roles, getting started | | Seasonal | Weeks of intense focus between busy periods | Researchers, founders, writers | | Team focus hours | Whole team pauses meetings and chat for set hours | Teams sharing calendars | ## When to use, and when not to Use it when important work keeps getting pushed aside, the day is fragmented, notifications dominate, a big piece of thinking work is due, or a team wants protected focus time. Don't use it to treat attention difficulties that may need assessment; suggest a qualified professional while still offering practical strategies. Don't use it to ignore real responsibilities such as on-call duties or customer commitments. ## Inputs - The important work that needs focus. - Calendar and typical meeting pattern. - Main sources of interruption (chat, email, phone, colleagues, home). - Energy pattern: when the person thinks best. - Role demands: response expectations, on-call, management. ## Workflow ### Step 1. Choose deep-work tasks List work that needs sustained thinking: writing, analysis, strategy, design, coding, learning. Link each to a goal. ### Step 2. Pick the pattern and times Match the pattern to the role; place blocks in high-energy hours. ### Step 3. Book and protect the blocks Recurring calendar events with a clear title, such as "Focus: Q4 report". Decline or move meetings that collide, with alternatives offered. ### Step 4. Set expectations Tell the team when focus blocks happen and how to reach the person for real emergencies. A status message such as "Focusing until 11, call for urgent issues" works well. ### Step 5. Prepare the environment Notifications off, phone in another room, one window open, materials ready, water nearby, a notepad to park stray thoughts. ### Step 6. Start with a ritual The same short start each time: open the task, write the goal for the block, set a timer. ### Step 7. Handle interruptions Park thoughts on the notepad; check messages only at the end of the block; for unavoidable interruptions, write one line about where you were before switching to reduce attention residue. ### Step 8. Close and review At the end, note what was done and the next step. Weekly, count focus hours and adjust. ## Interruption reduction checklist - Turn off non-essential notifications on desktop and phone. - Close email and chat during focus blocks. - Use do-not-disturb and focus modes, with exceptions for key people. - Batch email and chat into two to four windows a day. - Agree response-time norms with the team (for example, chat replies within two hours, urgent issues by phone). - Move recurring meetings to one part of the day. - Use website or app blockers if needed. ## Output format ``` 1. Deep-work tasks linked to goals 2. Focus pattern and weekly schedule 3. Calendar blocks and meeting changes 4. Team message on focus times and urgent contact 5. Environment and start ritual 6. Message batching windows and response norms 7. Weekly focus hours target and review question ``` ## Using AI agents during focus time Agents can protect focus as well as break it. Useful patterns: ask the agent to prepare materials and summaries before the block starts, hand it research questions to answer while you work on something else, and review its output after the block rather than checking in constantly. Turn off agent notifications during focus time, just like chat. ## Breaks and energy Focus depends on energy. Short breaks between blocks, a walk, water and daylight help people return sharper. Two to four hours of real deep work a day is a strong result for most people; trying to force eight usually backfires. When concentration fades early every day, check sleep, workload and stress before adding more techniques. ## Team focus hours Teams can agree shared focus hours, for example 9 to 11 on Tuesdays and Thursdays, with no meetings and chat on pause except for incidents. Write the norm down, add it to calendars, review it monthly and adjust for time zones in distributed teams. ## Working from home At home, agree focus hours with the people you live with, use a consistent spot that signals work, and keep household tasks out of focus blocks by listing them for a set time later in the day. ## Edge cases and judgement calls | Situation | What to do | |---|---| | Manager or support role | Shorter blocks, early morning or late afternoon; protect two longer blocks weekly | | Open-plan office or busy home | Headphones, booked rooms, or focus at quieter times | | Team culture of instant replies | Agree norms openly; start with one protected block a day | | Focus blocks keep getting booked over | Mark them busy; move them, never delete them | | Hard to start | Begin with a 25-minute sprint on the smallest part | | Energy crashes | Shorter blocks, breaks, movement; check sleep and workload | ## Handoffs to related skills - Scheduling the blocks: `time-blocking` - What deserves focus: `prioritisation`, `goal-setting-okrs` - Getting started: `procrastination-unblocking` - Focus routines: `habits-routines` - Fewer emails during focus time: the Email and Inbox skills ## Worked example An analyst had back-to-back meetings and never finished a quarterly model. The plan moved recurring meetings to afternoons, booked 9 to 11 focus blocks on four days, set chat to do-not-disturb with a status message, batched email at 11:30, 2 and 4:30, and kept a notepad for stray thoughts. The team agreed urgent issues come by phone. Focus hours rose from about three to ten a week, and the model was finished two weeks early. ## Common mistakes - Waiting for free time instead of booking it. - Starting a block without choosing the task. - Leaving notifications on and relying on willpower. - Checking messages "quickly" mid-block. - Copying someone else's focus pattern that does not fit the role. ## Measuring focus Count focus hours each week and the important outputs finished. Aim to grow focus hours steadily rather than jump to an ideal. If hours drop, look for the cause in the weekly review: meetings, interruptions, unclear tasks or fatigue. ## Self-check before you answer - Are focus blocks booked in high-energy hours? - Does each block have a chosen task? - Are interruptions reduced at the source? - Do the team know the norms and urgent route? --- Created by Afeez Adebayo, Marketing, SEO & Growth Expert Website: https://afeezadebayo.com LinkedIn: https://www.linkedin.com/in/afeez-adebayo/ X: https://x.com/za_icon Source: https://afeezadebayo.com/skills-md/productivity/planning-tasks/focus-deep-work/ Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). You may copy, share and adapt this skill, including for commercial use, as long as you credit Afeez Adebayo and link to the source URL above. Keep this notice in any copy or adapted version.
Workflow
Step 1. Choose deep-work tasks
List work that needs sustained thinking: writing, analysis, strategy, design, coding, learning. Link each to a goal.
Step 2. Pick the pattern and times
Match the pattern to the role; place blocks in high-energy hours.
Step 3. Book and protect the blocks
Recurring calendar events with a clear title, such as "Focus: Q4 report". Decline or move meetings that collide, with alternatives offered.
Step 4. Set expectations
Tell the team when focus blocks happen and how to reach the person for real emergencies. A status message such as "Focusing until 11, call for urgent issues" works well.
Step 5. Prepare the environment
Notifications off, phone in another room, one window open, materials ready, water nearby, a notepad to park stray thoughts.
Step 6. Start with a ritual
The same short start each time: open the task, write the goal for the block, set a timer.
Step 7. Handle interruptions
Park thoughts on the notepad; check messages only at the end of the block; for unavoidable interruptions, write one line about where you were before switching to reduce attention residue.
Step 8. Close and review
At the end, note what was done and the next step. Weekly, count focus hours and adjust.
Interruption reduction checklist
- Turn off non-essential notifications on desktop and phone.
- Close email and chat during focus blocks.
- Use do-not-disturb and focus modes, with exceptions for key people.
- Batch email and chat into two to four windows a day.
- Agree response-time norms with the team (for example, chat replies within two hours, urgent issues by phone).
- Move recurring meetings to one part of the day.
- Use website or app blockers if needed.
Output format
1. Deep-work tasks linked to goals
2. Focus pattern and weekly schedule
3. Calendar blocks and meeting changes
4. Team message on focus times and urgent contact
5. Environment and start ritual
6. Message batching windows and response norms
7. Weekly focus hours target and review questionUsing AI agents during focus time
Agents can protect focus as well as break it. Useful patterns: ask the agent to prepare materials and summaries before the block starts, hand it research questions to answer while you work on something else, and review its output after the block rather than checking in constantly. Turn off agent notifications during focus time, just like chat.
Breaks and energy
Focus depends on energy. Short breaks between blocks, a walk, water and daylight help people return sharper. Two to four hours of real deep work a day is a strong result for most people; trying to force eight usually backfires. When concentration fades early every day, check sleep, workload and stress before adding more techniques.
Team focus hours
Teams can agree shared focus hours, for example 9 to 11 on Tuesdays and Thursdays, with no meetings and chat on pause except for incidents. Write the norm down, add it to calendars, review it monthly and adjust for time zones in distributed teams.
Working from home
At home, agree focus hours with the people you live with, use a consistent spot that signals work, and keep household tasks out of focus blocks by listing them for a set time later in the day.
Edge cases and judgement calls
| Situation | What to do |
|---|---|
| Manager or support role | Shorter blocks, early morning or late afternoon; protect two longer blocks weekly |
| Open-plan office or busy home | Headphones, booked rooms, or focus at quieter times |
| Team culture of instant replies | Agree norms openly; start with one protected block a day |
| Focus blocks keep getting booked over | Mark them busy; move them, never delete them |
| Hard to start | Begin with a 25-minute sprint on the smallest part |
| Energy crashes | Shorter blocks, breaks, movement; check sleep and workload |
Handoffs to related skills
- Scheduling the blocks:
time-blocking - What deserves focus:
prioritisation,goal-setting-okrs - Getting started:
procrastination-unblocking - Focus routines:
habits-routines - Fewer emails during focus time: the Email and Inbox skills
Worked example
An analyst had back-to-back meetings and never finished a quarterly model. The plan moved recurring meetings to afternoons, booked 9 to 11 focus blocks on four days, set chat to do-not-disturb with a status message, batched email at 11:30, 2 and 4:30, and kept a notepad for stray thoughts. The team agreed urgent issues come by phone. Focus hours rose from about three to ten a week, and the model was finished two weeks early.
Common mistakes
- Waiting for free time instead of booking it.
- Starting a block without choosing the task.
- Leaving notifications on and relying on willpower.
- Checking messages "quickly" mid-block.
- Copying someone else's focus pattern that does not fit the role.
Measuring focus
Count focus hours each week and the important outputs finished. Aim to grow focus hours steadily rather than jump to an ideal. If hours drop, look for the cause in the weekly review: meetings, interruptions, unclear tasks or fatigue.
Self-check before you answer
- Are focus blocks booked in high-energy hours?
- Does each block have a chosen task?
- Are interruptions reduced at the source?
- Do the team know the norms and urgent route?
On this page
- When to use this skill, and when not to
- Example prompts
- Example output
- What the agent needs from you
- How this skill hands off to related skills
- How to run Focus and Deep Work step by step
- Situations this skill handles
- What makes this skill different
- Practical tips from real projects
- Frequently asked questions
- Changelog
When to use this skill, and when not to
Use it when important work keeps getting pushed aside, your day is fragmented by meetings and messages, a big piece of thinking work is due, or your team wants protected focus hours.
Research found interrupted workers compensate by working faster but report more stress, and switching tasks leaves attention residue that lowers performance on the next task.
Don’t use it to treat attention difficulties that may need assessment; the skill suggests qualified support while offering practical strategies.
Example prompts
- “I cannot focus. Help me protect time for deep work.”
- “Design focus blocks around my meeting-heavy week.”
- “Write a message to my team about focus hours.”
- “Help me batch email and chat.”
- “Set up team focus hours across two time zones.”
Example output
The skill returns a fixed structure. A shortened example for an imaginary site:
Deep work: quarterly model, strategy memo Pattern: daily 9 to 11 focus blocks, four days a week Meetings: moved to afternoons Norms: chat do-not-disturb; urgent issues by phone Batching: email at 11:30, 2:00 and 4:30 Target: 10 focus hours a week, reviewed on Fridays
Each focus block has a chosen task before it starts, and interruptions are reduced at the source rather than resisted with willpower.
What the agent needs from you
The skill asks for the work that needs focus, your calendar and meeting pattern, your main interruptions, when you think best and your role demands such as response expectations and on-call duties.
How this skill hands off to related skills
Focus and Deep Work connects to Habits and Routines, Goal Setting and OKRs, Project Breakdown and the Weekly Review, plus time blocking and prioritisation in the Planning and Task Management skills.
How to run Focus and Deep Work step by step
- Install the skill as
focus-deep-work/SKILL.md. - List work that needs focus.
- Pick a focus pattern for your role.
- Book blocks and tell your team.
- Turn off triggers before each block.
- Count focus hours weekly.
Situations this skill handles
Focus is hard in real jobs. The skill handles these:
| Situation | What the skill does |
|---|---|
| Manager or support role | Shorter blocks, two long ones weekly |
| Open office or busy home | Headphones, rooms, quieter times |
| Instant-reply culture | Norms agreed openly |
| Blocks booked over | Marked busy, moved not deleted |
| Hard to start | 25-minute sprint |
| Energy crashes | Shorter blocks, breaks, workload check |
What makes this skill different
Most focus advice is about willpower. This skill changes the setup: calendar blocks booked before the week fills, notifications removed, messages batched and team norms agreed, so focus no longer depends on resisting distractions.
It also fits the pattern to your role instead of copying someone else's routine.
Practical tips from real projects
- Focus is scheduled, not found.
- One task per block.
- Remove triggers.
- Batch the shallow work.
A worked example: an analyst had back-to-back meetings and never finished a quarterly model. The plan moved recurring meetings to afternoons, booked 9 to 11 focus blocks on four days, set chat to do-not-disturb with a status message, batched email at 11:30, 2 and 4:30 and kept a notepad for stray thoughts. The team agreed urgent issues come by phone. Focus hours rose from about three to ten a week, and the model was finished two weeks early.
Five focus patterns fit different roles. A daily block of 90 to 120 minutes at the same time suits most knowledge workers. One or two meeting-free focus days suit writers, engineers and designers. Sprints of 25 to 50 minutes with short breaks suit interruptible roles and help with getting started. Seasonal focus suits researchers and founders between busy periods. Team focus hours pause meetings and chat for everyone at agreed times.
The workflow chooses deep-work tasks linked to goals, picks the pattern and high-energy times, books and protects recurring blocks with clear titles, tells the team when blocks happen and how to reach the person in a real emergency, prepares the environment, starts each block with a short ritual, parks stray thoughts and messages until the end, and reviews focus hours weekly.
The interruption checklist turns off non-essential notifications, closes email and chat during blocks, uses do-not-disturb with exceptions for key people, batches messages into two to four windows a day, agrees response norms, groups recurring meetings and adds blockers if needed.
When an interruption cannot wait, writing one line about where the work stopped reduces attention residue and makes it easier to return. AI agents can protect focus too: they can prepare materials before a block and answer research questions while the person works, with their notifications off until the block ends.
Energy matters as much as time. Short breaks, movement and water help, and two to four hours of real deep work a day is a strong result for most people. When concentration fades early every day, the skill points to sleep, workload and stress before adding more techniques, and at home it suggests agreed focus hours with household members and a consistent workspace.
Focus works differently by role. Managers and support leads use shorter blocks at the start or end of the day and protect two longer blocks a week. People in open offices or busy homes use headphones, booked rooms or quieter hours. Teams used to instant replies agree norms openly and begin with one protected block a day, and blocks that keep getting booked over are marked busy and moved rather than deleted. When starting is the problem, a 25-minute sprint on the smallest part of the task usually breaks the deadlock, and team focus hours across time zones are written down, added to calendars and reviewed monthly.
Progress is measured as focus hours and important outputs finished each week, growing steadily rather than jumping to an ideal schedule.
Frequently asked questions
What is deep work?
Focused, distraction-free work on cognitively demanding tasks, a term popularised by Cal Newport.
How long should a focus block be?
Often 90 to 120 minutes, or 25 to 50-minute sprints for interruptible roles or getting started.
How many hours of deep work are realistic?
Two to four hours a day is a strong result for most people.
How do I stop interruptions?
Turn off notifications, close email and chat, batch messages and agree response norms with your team.
What is attention residue?
The part of your attention that stays on a previous task after switching, which lowers performance on the next.
Can managers do deep work?
Yes, with shorter blocks at the edges of the day and two longer blocks protected each week.
Changelog
- 1.0.0, 10 October 2026: first release.
Use, adapt and share this skill under CC BY 4.0: credit Afeez Adebayo and link to this page.
