Attention
Plan your day and keep it in view. Today's three, what slipped, the week and month, the roadmap in flight, who is waiting on you, your standup, and a checklist of where every session stands.
In short
The attention skill turns your task board into a short view of today, the week and the month, and who is waiting on you, and it writes your standup. Start by asking "what should I work on?", which proposes up to three things for today and waits for your yes.
A long task board is a backlog, not a plan. The attention skill turns it into a view you can glance at: up to three things for today, what carried over, what the week and month are for, the roadmap milestones in flight, and who is waiting on you. It also writes your standup and keeps a checklist of where each session stands.
Ask in plain words, or name the skill and a playbook (attention plan). Skills shows how to run one on your host, and Daily rhythm shows where each playbook sits in a day.
What to ask
| Playbook | Ask | You get |
|---|---|---|
| refresh | "what's waiting on me", attention, attention <project> | The queue pulled fresh, the view re-rendered, and a short card |
| add | "take this on", attention add <text or link> | A new task, planned for a period |
| plan | "plan my day", "what should I work on", attention plan | Today cut to three |
| organize | "I'm overwhelmed", "get organized", attention organize | Your head emptied and sorted, then today cut to three |
| standup | "standup is coming up", attention standup 48 | Did, next, and blocked as a card |
| checkpoint | "checkpoint this session", "where are we in this session", attention checkpoint | The session you're in as a checklist |
| checkpoint all | "what was I working on", "which session needs me", attention checkpoint all 48 | Every recent session as a checklist, decisions waiting on you first |
| backfill | first refresh, Slack connected | The priorities already posted in Slack, triaged into tasks you confirm |
attention help lists them. Nothing is created or moved without your answer, and attention never comments on, reviews, or merges anything.
Where it shows
| You run | Where it shows | Holds |
|---|---|---|
attention | the dashboard's Today → Attention tab (dashboard.html#today/attention) | every project, plus today's, the week's and the month's goals |
attention <project> | projects/<project>/attention.html | that project's tasks only |
The view is derived. Tasks, goals, and roadmaps are its source of truth, and it re-renders on every task change, so there is nothing to save. Today walks through the home view. A project's page is linked from its project card. It exists once you first run attention for that project, and every rebuild keeps it current.
Plan the day
attention plan proposes today's three, each with its reason. It picks from:
- carried-over work, and anything due;
- sessions you already started;
- replies you owe;
- tasks behind the roadmap's milestones;
- the week's P0 and P1 tasks.
Tasks that serve today's goals, set with goals day, rank first. Once you confirm the three, it settles each carried-over item (this week, later, drop, or keep) and offers a task for any roadmap milestone nothing on the board moves forward.
Setting and scoring goals is the goals skill, since goals are outcomes and attention is tasks. See Goals.
Plans date themselves
A plan is stored on the task as its horizon: the period it is planned for. Say today, week, next-week, month, or later and the agent stores the period. Because the date is in the plan, nothing has to roll over at midnight: once its period ends, the task reads as carried over.
Two rules keep the lanes honest:
- A task due today or earlier that nobody planned shows under Today in its own block, rather than hiding in a collapsed lane.
- Week and month progress count everything planned inside the period, including work since pulled into today and work sync has already archived.
Add work
Say "take this on", or run attention add with a line of text, a pasted list, a GitHub issue or pull request link, or a Slack link. The agent checks the board first, so the same work doesn't become two tasks. Then it drafts the task and asks one confirming question: which horizon it goes in.
When there's too much in your head
plan treats the board as the whole picture. On an overwhelmed day the real load is in your head and the board is too noisy to trust, so organize starts with your head.
-
It reads the board, silently: overdue tasks, unset week goals, a slipped milestone with no task behind it.
-
It asks what's on your mind, in plain chat: dump all of it, unsorted, and say whether the week is light, normal, or heavy.
-
It sorts the dump against your existing tasks, so nothing becomes a duplicate:
Bucket What happens Tracked Already a task; it gets a horizon if it has none New task Drafted and placed, the way adddoes itWaiting on someone A task only when you have to chase it Worry or note Not actionable now; captured to the inbox -
It asks only about the gaps it found, most urgent first: a new date for an overdue task, the week's goals when none are set (one on a heavy week, up to three on a light one), a task for a milestone nothing moves. Questions stop after three rounds.
-
It cuts today to three with
plan's ranking, except that something you raised outranks a board item in the same tier. A heavy week gets fewer than three.
The reply is a card, and the run is saved as a plans report:
🧹 Organized · Thu 1 Oct · heavy week
FIRST MOVE Reply to the vendor about the renewal quote
TODAY 1 Renewal quote reply (ac-014) 2 Fix the export timeout (ac-021)
WEEK Ship the export fix
PARKED Onboarding revamp (later) · Conference talk (not this week)
CAPTURED 3 new tasks · 5 already tracked · 4 notes to the inboxParked lists what this run moved to later, dropped, or left out of the week, so what isn't happening is written down too. Worries and notes go to the inbox in one capture, so the next compile keeps them and you don't have to. When the board has a large stale pile, organize offers to settle it another time rather than adding a second job to a bad day.
The queue
The queue is who is waiting on you. It is pulled when you run attention and shown with the time it was pulled:
- My pull requests, with review state, mergeability, and age, from the GitHub pack.
- Reviews I owe, and how long each has waited.
- Replies I owe, with the Slack pack: mentions of you that have gone an hour without your answer.
- External threads waiting, with the Slack pack: threads in your shared channels where someone outside the workspace has waited an hour or more. Channels you've joined that the channel map doesn't list yet show as a note under this group. Slack has the exact rules for both.
A source that can't be read says so once, under its group, rather than showing an empty, reassuring list; the note never counts as an item. On a project page the queue narrows to the repo (and channels) the project's README names.
The roadmap
The home view reads your north-star roadmap.html. A project page reads its own roadmap, plus the north-star milestones that name one of the project's task ids. The Roadmap section lists the milestones that matter now:
- Slipped: the period ended with items open. These come first.
- In flight: an item is in progress, or the period covers today.
Each shows how far along it is, the tasks its text names and where they stand, and a flag when no open task is behind it. That gap is what attention plan offers to fill.
Standup
"Standup is coming up", or attention standup, builds what you did, what's next, and what's blocked from git, pull requests, sessions, and the board, as a card to glance at while you talk. attention standup 48 widens the window from the last 24 hours. Standup shows the card and what it saves.
Checkpoints
attention checkpoint maps the session you're in as a checklist: done steps with their proof, what's in progress, the next step, and the decisions waiting on you. attention checkpoint all does the same for every recent session, the waiting decisions first, and saves the session radar the dashboard and briefings read. Checkpoints has an example of each.
The data in the pages
Attention views and roadmaps keep what they show as JSON inside the page, so another skill, a script, or another agent can read it without rendering anything.
The blocks, their shapes and the roadmap's dates are below, for when you write a script or tool that reads them.