Sign inGet started
Skills / Productivity-habits

The Pomodoro Technique

A pomodoro is indivisible. If it is interrupted definitively, it must be abandoned and a new one started later.

The Pomodoro Technique is Francesco Cirillo's official time-boxing system built around 25-minute focused work intervals, structured breaks, and a daily planning and review ritual. Unlike the popular 'just set a timer' shortcut, Cirillo's full framework includes the Activity Inventory, the To-Do Today Sheet, rules for decomposing large tasks and grouping small ones, and a precise protocol for handling interruptions without breaking focus. It is designed for knowledge workers, students, and remote professionals who want to plan realistic workdays, protect their concentration, and steadily improve their ability to estimate effort.

By Francesco Cirillo · Free
Specimen 01 · Live diagnosisThe Pomodoro Technique
Input

“I have to finish the Q2 budget analysis, reply to a backlog of emails, prep for a 2pm stakeholder call, review a teammate's PR, and I've been meaning…”

Diagnosis
Let's build your To-Do Today Sheet using Cirillo's full planning process — not just a timer, but a realistic daily plan with pomodoro estimates.
Full transcript ↓
Calibrated referenceagent-skills.ai
The gap

Work with time, not against it — plan your day in focused 25-minute intervals

Cirillo's framework operates on a precise repeatable cycle: choose a task from the Activity Inventory, set the timer for 25 minutes (one pomodoro), work with undivided focus until the timer rings, record an X on the To-Do Today Sheet, take a 5-minute short break, and after every four pomodoros take a 15–30 minute long break. The full methodology goes well beyond this surface cycle: tasks exceeding five to seven pomodoros must be decomposed into subtasks before they appear on the daily sheet; tasks taking less than one pomodoro are grouped with similar small tasks. Interruptions are classified as internal (self-generated) or external (triggered by others), and external interruptions are handled with the Inform-Negotiate-Call Back protocol to protect the active interval without ignoring the request. Each day closes with a retrospective comparing estimated pomodoro counts against actuals, building estimation accuracy over time. The To-Do Today Sheet is the central daily artifact: it captures tasks, estimates, actuals, and interruption tallies in one form.

The problem

Most people who 'use the Pomodoro Technique' are only using the timer — they miss the planning layer that makes it a real system. Without the To-Do Today Sheet, task sizing rules, and interruption protocol, practitioners still start their days with an undefined pile of work, accept every interruption without a framework, and have no way to know whether their time estimates are improving or drifting. The timer alone cannot solve overcommitment, task ambiguity, or the 'Void' — Cirillo's term for the discomfort that drives self-interruption during focused work.

The solution

Apply Cirillo's full methodology — not just a countdown clock — to plan a focused workday, protect active intervals from internal and external interruptions, and build the estimation accuracy that lets you reliably know what you can finish before 5pm.

You bring
  • Your task list or backlog for the day (even if unordered or vague)
  • Recent interruptions or focus blockers you want to address
  • Any history of how long tasks actually took vs. how long you expected
  • Your available working hours or time constraints for the day
You get
  • A completed To-Do Today Sheet with tasks, pomodoro estimates, and a realistic daily plan
  • Decomposed versions of any oversized tasks and grouped versions of small ones, sized to fit clean pomodoro slots
  • A ready-to-apply Inform-Negotiate-Call Back script for your most common interruption type
  • An end-of-day retrospective comparing your estimates against actuals with patterns surfaced
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

It's 9am. You have seven things on a mental list, two of them huge and undefined. By 11am you've switched contexts four times, answered eight Slack messages mid-task, and the budget analysis is still open in a tab. You have no idea how much of the day is left or what you'll actually finish.

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

You start the day with a To-Do Today Sheet: six tasks, seven pomodoros estimated, sequenced in order. You know the onboarding doc has been decomposed and only one section is on today's sheet. When your manager Slacks you during the second pomodoro, you reply 'wrapping something up, back to you in 18 min' and finish the interval. At 5pm your sheet shows seven estimated vs. nine actual pomodoros — the retrospective reveals variance analysis always takes longer than planned. Tomorrow's estimate for that task type goes up.

The same situation once the methodology holds.
Fig.02A real session, unedited
In-app · assistant
The Pomodoro TechniqueClaude
The Pomodoro Technique
Let's build your To-Do Today Sheet using Cirillo's full planning process — not just a timer, but a realistic daily plan with pomodoro estimates. What's on your plate today? Give me your raw task list, even if it's messy or partially formed.
I have to finish the Q2 budget analysis, reply to a backlog of emails, prep for a 2pm stakeholder call, review a teammate's PR, and I've been meaning to write up a process doc for onboarding.
Good — five items. Before we estimate, I need to size them. The Q2 budget analysis and the onboarding process doc both sound like they could be large. How far along is the budget analysis, and roughly how many sections or sub-pieces does the process doc need to cover? I'm checking whether either of these needs to be decomposed before it goes on today's sheet — Cirillo's rule is that anything over five to seven pomodoros must be broken into subtasks.
The budget analysis is about 60% done — I just need to finish the variance section and write the summary. The process doc is a full first draft from scratch, probably long.
That shapes things clearly. The budget analysis remainder — variance section plus summary — sounds like two to three pomodoros: manageable as a single item. The onboarding process doc is a different story. A full first draft from scratch is almost certainly more than seven pomodoros, which means it cannot go on today's sheet as one task. We need to decompose it. What are the discrete sections it needs? Even rough section names will do — we'll assign pomodoro estimates to each piece separately, and you'll put only what fits today onto the sheet.
Probably: intro and overview, tools setup steps, first-week checklist, team contacts section. Four sections.
Perfect decomposition — four discrete subtasks. I'd estimate the intro/overview and tools setup at one to two pomodoros each, the first-week checklist at two, and the team contacts section at one. That's six to seven pomodoros total for the full doc — which confirms it couldn't have lived on one day's sheet as a single task. Now here's your To-Do Today Sheet with the other items sized in:
| Task | Estimate ||---|---|| Q2 budget: variance section | 2 🍅 || Q2 budget: executive summary | 1 🍅 || Email backlog triage | 1 🍅 || Stakeholder call prep | 1 🍅 || PR review (teammate) | 1 🍅 || Onboarding doc — intro & overview | 1 🍅 |
Total: 7 pomodoros — about 3.5 hours of focused work plus breaks. Does that fit your available time today, or do we need to move an item to the Activity Inventory for tomorrow?
That fits. But I know I'll get interrupted constantly by Slack messages from my manager during the budget work. That's always what kills my focus on deep tasks.
That's a classic external interruption pattern — and Cirillo has an explicit protocol for it: Inform, Negotiate, Call Back. When your manager messages you during a pomodoro, here's the script: Inform — 'I'm in the middle of something right now.' Negotiate — 'Can I get back to you in 20 minutes?' Call Back — and then actually do it when the pomodoro ends. The key is that you're not ignoring the request, you're deferring it to the break with a committed time. The pomodoro stays intact. Do you want to rehearse the phrasing for your specific manager so it feels natural rather than scripted?
Reply to The Pomodoro Technique
What the skill is doing
01To-Do Today Sheet Builder
02Task Sizing Coach
03Interruption Protocol Advisor
Fig.03The same skill, in the channel you already use
WhatsApp · live
9:41
TPThe Pomodoro Techniquetyping…
Messages are end-to-end encrypted. No one outside of this chat can read them.
Today
I have to finish the Q2 budget analysis, reply to a backlog of emails, prep for a 2pm stakeholder call, review a teammate's PR, and I've been meaning…9:14✓✓
Let's build your To-Do Today Sheet using Cirillo's full planning process — not just a timer, but a realistic daily plan with pomod…9:14
Give me your raw task list, even if it's messy or partially formed.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

To-Do Today Sheet Builder

Takes your raw task list and builds a structured daily plan in the form of Cirillo's To-Do Today Sheet — with each task labeled, estimated in pomodoros, and sequenced for the day. The output is a single reference form you track throughout the day, recording actual pomodoros and interruptions alongside estimates.

Based on Cirillo's official To-Do Today Sheet, which pairs every task with an estimate column and an actuals column, creating a closed-loop daily planning and review artifact.
CapabilityC-02

Task Sizing Coach

Evaluates each task on your list for pomodoro size: tasks that would take more than five to seven pomodoros are flagged and decomposed into subtasks; tasks smaller than a single pomodoro are grouped with similar small items. This prevents the common failure mode of putting an unbounded task on the daily sheet and never finishing it.

Implements Cirillo's explicit task sizing rules — decompose tasks exceeding five to seven pomodoros, combine tasks requiring less than one — which are a formal part of the technique's planning phase and absent from most popular interpretations.
CapabilityC-03

Interruption Protocol Advisor

Classifies an interruption you describe as internal (a thought, urge, or distraction you generated yourself) or external (a colleague, message, or request from outside). For internal interruptions it applies the 'record and return' strategy; for external ones it walks through Cirillo's Inform-Negotiate-Call Back protocol to defer the request without ignoring it.

Directly applies Cirillo's internal/external interruption taxonomy and the Inform-Negotiate-Call Back framework, which prescribes telling the interrupter you're occupied, negotiating a specific callback time, and following through — preserving the active pomodoro.
CapabilityC-04

Pomodoro Estimation Trainer

Helps you estimate effort for new tasks by comparing them to task types you have historical actuals for. Over time, guides you toward building a personal estimation baseline — knowing, for example, that your 'write a report section' tasks consistently take three pomodoros rather than the one you originally planned.

Rooted in Cirillo's retrospective review practice, which explicitly compares estimated vs. actual pomodoro counts to surface systematic over- or under-estimation and improve daily planning accuracy session over session.
CapabilityC-05

End-of-Day Retrospective

Closes your workday by reviewing the completed To-Do Today Sheet — comparing every estimate against its actual, counting interruptions, and identifying which task types are hardest to estimate. Produces a short set of insights and one adjustment to carry into tomorrow's planning session.

Implements Cirillo's daily retrospective ritual, the final stage of his official technique cycle, in which the practitioner analyzes the day's data to improve the system rather than simply repeat it.
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 planning form listing each task with its estimated pomodoro count, actual pomodoro count (filled in as the day progresses), and an interruption tally. The completed sheet at day's end is both a productivity record and the raw material for the retrospective.

OutputD-02

Task Decomposition Map

A breakdown of any tasks flagged as too large (more than five to seven pomodoros), showing how each oversized item splits into concrete subtasks that each fit within clean pomodoro slots — ready to place on the To-Do Today Sheet.

OutputD-03

Interruption Log

A tally and classification of interruptions encountered during the day, distinguishing internal from external, with the protocol applied to each external one and the outcome recorded. Reveals patterns in what breaks your focus most often.

OutputD-04

Estimation Accuracy Report

A side-by-side comparison of estimated vs. actual pomodoros for every task completed, with a summary of which task types are consistently over- or under-estimated and a single calibration recommendation for tomorrow's 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 invented the Pomodoro Technique in the late 1980s as a university student in Rome, naming it after a tomato-shaped kitchen timer he used to battle procrastination and distraction. He has since formalized the method into a comprehensive book, a set of certified training programs, and international workshops delivered through his consultancy, the Cirillo Company. The technique is now one of the most widely documented productivity frameworks in the world, with official certified trainers and organizational clients across multiple countries.

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

The Pomodoro Technique (official book and methodology)

by Francesco Cirillo

Inventor of the Pomodoro Technique; founder of the Cirillo Company; certified trainer network; official book translated into multiple languages.

Read the original ↗
Citationfrancescocirillo.com
In the build queue

Be first to run it.

The Pomodoro Technique is being built right now. Leave your email and we’ll tell you the moment it goes live.

Notify meEmail
At launchI want to plan today using the real Pomodoro Technique — not just a timer. Here's my task list: [paste your tasks]. Can we build a To-Do Today Sheet with pomodoro estimates and flag anything that needs to be decomposed?