Sign inGet started
Skills / Productivity-habits

Pomodoro Technique

A Pomodoro is indivisible. If it is interrupted, it must be abandoned.

The Pomodoro Technique is a time management method that breaks work into discrete 25-minute focused intervals — called pomodoros — separated by short breaks, with a longer rest after every four. Developed by Francesco Cirillo, it transforms abstract, anxiety-producing time into a concrete, measurable ally by making effort visible through tracked units. It is for anyone who struggles with procrastination, distraction, or chronic underestimation of how long things actually take.

By Francesco Cirillo · Free
Specimen 01 · Live diagnosisPomodoro Technique
Input

“I need to finish a quarterly report, reply to a backlog of emails, prep a slide deck for Thursday, do a code review, and I keep saying I'll organize…”

Diagnosis
Let's build your To-Do Today sheet.
Full transcript ↓
Calibrated referenceagent-skills.ai
The gap

Work with time, not against it — one 25-minute pomodoro at a time

The Pomodoro Technique operates through a five-stage daily cycle: Record tasks on an Activity Inventory, Estimate how many 25-minute pomodoros each task requires, Track completed pomodoros with checkmarks on a To-Do Today sheet, Process interruptions (marking internal distractions with an apostrophe, external ones with a dash), and Visualize patterns weekly to improve future estimates. Each pomodoro is treated as indivisible — if significantly interrupted, it is voided and restarted. After four consecutive pomodoros, a 15–30 minute break resets cognitive capacity. Over time, comparing estimated vs. actual pomodoros turns vague task guesses into calibrated plans.

The problem

Most people treat time as an abstract enemy — tasks feel overwhelming, procrastination creeps in, and the day ends with more on the list than when it started. Interruptions fragment focus so thoroughly that deep progress feels impossible, yet there is no system to make the true cost of distractions visible. Without a concrete unit of effort, time estimates are pure fiction.

The solution

Turn each workday into a series of clear, protected 25-minute commitments — making effort tangible, interruptions visible, and your relationship with time something you can actually improve.

You bring
  • A list of tasks or projects you need to work through today
  • Your current distractions and interruption patterns
  • Your available time window and energy level
  • A commitment to working in focused, unbroken intervals
You get
  • A structured To-Do Today sheet with realistic pomodoro estimates per task
  • An Interruption Log that makes your true distraction costs visible
  • A completed Pomodoro Record showing effort invested across the day
  • Calibrated future estimates as you track estimated vs. actual pomodoros over time
In action

Watch the methodology work.

Three specimens from a single real session: the same situation, before and after, the full transcript, and the skill answering live in the channel where the work happens.

Fig.01The same situation, two ways
Specimens A · B
Specimen ABefore
Without the skill

You sit down to work on the quarterly report. An hour passes and you've opened the document, replied to three Slack messages, started a separate email, looked up a statistic, and written one paragraph. You're not sure if you made progress. Your calendar says the report is due Thursday and you have no idea if you're on track.

×The situation as it arrives — before the methodology is applied.
Specimen BAfter
With Pomodoro Technique

You open your To-Do Today sheet and see the quarterly report assigned 3 pomodoros. You launch the first one. When a Slack message arrives mid-session, you add a dash to your sheet and send a quick 'in a session, back at 10:30' reply. At the end of the day your record shows 3 completed pomodoros on the report (matching your estimate), 2 on the deck (1 under estimate — the task was simpler than expected), and 4 external interruption dashes — all from one teammate. You know exactly where you stand and exactly where your focus is leaking.

The same situation once the methodology holds.
Fig.02A real session, unedited
In-app · assistant
Pomodoro TechniqueClaude
Pomodoro Technique
Let's build your To-Do Today sheet. Tell me the tasks on your plate right now — don't filter or prioritize yet, just give me the full list. Once we have them out, we'll estimate pomodoros for each and figure out what actually fits in today's available hours.
I need to finish a quarterly report, reply to a backlog of emails, prep a slide deck for Thursday, do a code review, and I keep saying I'll organize my project notes but never do.
Good. Now let's estimate. For each task, I want your gut reaction first — how many 25-minute pomodoros do you think it will take? Don't overthink it. Quarterly report first: how many?
The report... maybe 3? The emails probably 1, the deck is hard to know — maybe 4? Code review 2, and the notes org I have no idea, maybe 2.
That's 12 pomodoros estimated — about five hours of focused work plus breaks. A realistic deep-work day is 8–10 pomodoros. So something has to move to tomorrow or shrink. Here's what I notice: 'organize project notes' has no clear deliverable, which usually means the estimate is wrong. What would 'done' actually look like for that task? If you can't define it in one sentence, it needs to be broken down before it earns a slot on today's sheet.
Huh — I think what I actually want is to create a single reference doc for the Henderson project. That I could probably do in 1 pomodoro.
Perfect. That's now a real task: 'Create Henderson project reference doc — 1 pomodoro.' Now your total is 11 estimated pomodoros. I'd suggest dropping the code review to tomorrow — it's the only item without a deadline pressure — and committing to 9 pomodoros today: report (3), deck (4), emails (1), Henderson doc (1). We'll track actuals as you go, and by Friday you'll start seeing whether your estimates are consistently off in any direction. Ready to launch your first pomodoro on the quarterly report?
Yes — but I already know I'm going to get interrupted by Slack messages. That always kills my focus.
That's an external interruption pattern, and it has a protocol. Before you start the timer: close Slack notifications, set your status to 'In a Pomodoro — back at [time]'. If someone interrupts anyway, use the four-step response: Inform ('I'm in a focused session'), Negotiate ('Can this wait 15 minutes?'), Schedule ('I'll message you at 11am'), Call back (actually do it on your break). If you can't defer it, the pomodoro is voided — you mark a dash on your sheet and restart fresh. That dash is data, not failure. Start collecting those dashes and you'll know exactly which meeting or person costs you the most focus time each week.
Reply to Pomodoro Technique
What the skill is doing
01Pomodoro Session Launch
02Daily To-Do Today Planning
03Interruption Shield Protocol
Fig.03The same skill, in the channel you already use
WhatsApp · live
9:41
PTPomodoro Techniquetyping…
Messages are end-to-end encrypted. No one outside of this chat can read them.
Today
I need to finish a quarterly report, reply to a backlog of emails, prep a slide deck for Thursday, do a code review, and I keep saying I'll organize m…9:14✓✓
Let's build your To-Do Today sheet.9:14
Tell me the tasks on your plate right now — don't filter or prioritize yet, just give me the full list.9:15
Once we have them out, we'll estimate pomodoros for each and figure out what actually fits in today's available hours.9:15
Message

The same skill, where the work happens.

No new app to learn. The methodology runs over the WhatsApp Business API, so the answer lands as a reply in the thread you’re already in — same rigour, zero context-switch.

Reads the situation, names the pattern, returns one concrete next move.
Delivered in seconds, inside a conversation that already exists.
Specimen · WhatsApp Business API · live
Capabilities

What it does, specifically.

Each capability is a distinct move drawn straight from the source methodology — not a generic assistant guessing.

CapabilityC-01

Pomodoro Session Launch

Guides you through starting a focused 25-minute interval: confirming your single task, clearing your environment, and committing to the timer. Provides a structured check-in when the interval ends to record completion and decide what is next.

Based on Cirillo's indivisibility principle — a pomodoro is a complete, atomic unit of work that cannot be split, making each launch a ritual commitment.
CapabilityC-02

Daily To-Do Today Planning

Helps you select tasks from your Activity Inventory for the day, estimate the number of pomodoros each will require, and sequence them to fit your available work time realistically.

Implements Cirillo's daily planning ritual using the To-Do Today sheet, where estimation forces task decomposition and surfaces hidden complexity before work begins.
CapabilityC-03

Interruption Shield Protocol

Coaches you through the 'Inform, Negotiate, Schedule, Call Back' protocol for external interruptions and helps you capture internal distractions as apostrophe marks — a promise to yourself to return to the thought later — so focus is preserved.

Directly applies Cirillo's interruption taxonomy: internal distractions (marked ') are deferred, external ones (marked -) are handled with a four-step protocol to protect the pomodoro without alienating colleagues.
CapabilityC-04

Estimation Calibration Tracking

Records your estimated pomodoro counts alongside your actual completions session by session, then surfaces the gap over time. When your estimates are consistently off, it helps you diagnose why — task ambiguity, hidden subtasks, chronic interruption — and adjust.

Implements the Record–Process–Visualize stages of Cirillo's five-stage cycle, where empirical data about effort replaces optimistic guesswork in future planning.
CapabilityC-05

Weekly Record Review

Facilitates a structured end-of-week reflection on your Pomodoro Records: how many pomodoros were completed, where estimates went wrong, which interruptions recurred, and what one adjustment would improve next week.

Based on Cirillo's progressive improvement principle — the technique is not a static timer but a practice refined weekly through honest review of recorded data.
Tested

Graded before it shipped.

Every skill is scored against independent scenarios for methodology fidelity before it goes live — not vibes, a rubric.

What it produces
OutputD-01

To-Do Today Sheet

A structured daily plan listing each selected task with its estimated pomodoro count and a row of boxes to check off as intervals are completed — making effort visible and progress tangible throughout the day.

OutputD-02

Interruption Log

A categorized record of every internal and external interruption across your sessions, showing which sources of distraction cost you the most pomodoros and where the 'Protect the Pomodoro' protocol is most needed.

OutputD-03

Pomodoro Record Sheet

A daily completion record using Cirillo's notation — checkmarks for finished pomodoros, apostrophes for internal distractions, dashes for external ones — creating a truthful account of where your time actually went.

OutputD-04

Estimation Calibration Report

A comparison of estimated vs. actual pomodoros per task over time, revealing whether you consistently under- or over-estimate certain types of work and enabling measurably better planning.

The source

Grounded in the original work.

Every answer traces back to a real source and the practitioner who wrote it — not a secondhand summary. Here is the source of record.

Source authorA-01

Francesco Cirillo

Francesco Cirillo developed the Pomodoro Technique as a university student in the late 1980s, using a tomato-shaped kitchen timer to fight his own procrastination and focus challenges. He went on to found XPLabs, a software consultancy, and now runs training workshops and certifications worldwide. His freely distributed book 'The Pomodoro Technique' has been downloaded millions of times and translated into dozens of languages.

Status · Inspired by Francesco Cirillo’s work — not yet claimed. Are you Francesco Cirillo?
Primary sourceS-01

The Pomodoro Technique

by Francesco Cirillo

Creator of the Pomodoro Technique; founder of XPLabs; consultant and trainer; author of the foundational technique book downloaded millions of times globally.

Read the original ↗
Citationen.wikipedia.org
Get started

Put it to work.

agent-skills runs as MCP — connect it once and Pomodoro Technique works in Claude, ChatGPT, Cursor, or any MCP-compatible client. Sign in to see your config and accept the terms.