How-to

xTiles End-of-Day Reflection: How to Automatically Summarize Your Workday with Claude

"It seems like it's now coming together — instead of just trying to figure it out manually, we can have Claude come in and create that." — Anthony, business consultant and ADHD coach

The blur of a busy day, especially with ADHD

Anthony and Jessica, who run a consulting business together, described a familiar feeling on this call: full inbox, a stream of Slack messages, a couple of meetings — and by the end of the day, a nagging sense that nothing actually got done, even though the day was clearly busy. Nothing about it got written down as a task, so nothing about it registers as progress.

Anthony's own framing for what he wanted was specific: not a dashboard — to him, that word means metrics and KPIs — but a command center. One page, everything about the day visible at once, without having to reconstruct it from memory at 6 p.m.

What an end-of-day reflection automation actually does

At a set time each evening, Claude — connected to xTiles via MCP, along with whatever else you use daily, like Slack, your inbox, or a meeting-notes tool — reviews everything you touched that day and writes back two things into your xTiles Planner: a short scope-of-day summary, and a set of tasks it creates and marks complete, reflecting work you actually did but never logged.

That second part is worth calling out directly, because it solves a specific pattern: a brain that has trouble feeling like a day was productive unless there's a checked box somewhere to point at. Watching five or six completed tasks appear automatically — real work, just never written down as it happened — closes that gap without requiring you to track anything during the day itself.

Setting it up: the prompt and the schedule

The setup is a single prompt, run on a schedule rather than something you have to remember to ask for each evening.

1

Connect your sources

Add the xTiles MCP connector in Claude, plus whatever else you use daily — Slack, your inbox, a meeting-notes tool — as Claude connectors, so there's a full picture of the day to review.

2

Write the reflection prompt

Something close to: "Review my day across Slack, my inbox, meeting notes, and xTiles. Give me a one- or two-sentence summary of what I actually worked on today. Then create xTiles tasks for the work I completed but never logged, and mark them done."

3

Turn it into a Scheduled Task or Routine

Set it to run automatically at the end of your workday — 5:30 p.m. is a natural choice — rather than triggering it manually. A cloud-based Routine means it still runs even if your laptop is closed by then.

4

Space out multiple automations

If you're also running a morning brief or a newsletter digest, stagger them by 15–30 minutes so each one has a clean window rather than competing for the same information at once.

The output lands as a tile on your daily Planner page, so it's already there the next time you open xTiles — not buried a few messages back in a chat thread.

Why this fits an ADHD-driven workday specifically

The command-center framing matters more than it might sound. A day reconstructed after the fact — Slack, inbox, meeting notes, and xTiles activity all pulled into one short summary — replaces the mental effort of trying to remember what happened with something you can just read. For anyone who has ever ended a day certain they got nothing done, only to realize on reflection that several real things happened, this automation is that reflection, done automatically.

It's also a genuinely two-person tool. Jessica, who leans toward metrics-and-KPI dashboards in her own work, and Anthony, who wanted a single visual command center, land on the same underlying data — each can read it the way that makes sense to them, without either having to adopt the other's system.

Beyond one day: weekly rollups and shared project logs

The same pattern extends past a single evening. A weekly version of the same prompt — reviewing the week's tasks, communications, and completed work — produces a rollup of what actually happened over five days instead of one, including a log of what shipped and what's still open.

For a team, the equivalent lives at the project level: a running log of what got accomplished during the week, pulled from tasks and communication inside that specific project, so a team's day is visibly more than just a day — it's a record of real progress, without anyone having to compile it by hand.

Frequently asked questions

What is an end-of-day reflection automation in xTiles?
It's a scheduled prompt that asks Claude — connected to xTiles and your other daily tools via MCP — to review everything you did that day and write back a short summary plus a set of completed tasks representing work you did but never logged, delivered as a tile in your daily Planner.
How do I set up a daily summary with Claude and xTiles?
Connect the xTiles MCP connector in Claude along with any other tools you use daily (Slack, inbox, meeting notes), write a prompt asking Claude to review your day and summarize it, then turn that prompt into a Scheduled Task or Routine set to run at the end of your workday.
Can Claude create and mark tasks complete based on what I actually did, not what I planned?
Yes. Ask it to review your day's activity across your connected tools and create xTiles tasks for work it finds evidence of, then mark those tasks done — a useful way to see real accomplishment that was never manually tracked.
What is a good prompt for an end-of-day recap?
Something like: "Review my day across Slack, my inbox, meeting notes, and xTiles. Give me a one- or two-sentence summary of what I actually worked on today. Then create xTiles tasks for the work I completed but never logged, and mark them done."
Should an end-of-day reflection run as a Scheduled Task or a Routine?
A Routine is more reliable for this specific use case, since it runs in the cloud and doesn't require your laptop to be open at 5:30 p.m. A Scheduled Task works too, but only while your device is on and running.
Can the same idea work for a weekly review instead of just a daily one?
Yes. The same prompt pattern, pointed at a week's worth of tasks and communication instead of a single day, produces a weekly rollup — what shipped, what's still open — and can be scoped to a specific project so a team can see a shared log of progress.