Welcome to the Productivity Coach
Thank you, and welcome.
You now own the agent that reads your work back to you. Your Knowledge Work Coach captures what you do; this one turns that record into a daily progress file, a weekly and monthly recap, a strategy file on your cadence, and the week's tasks in your Todoist. It also makes that work reachable from your phone or iPad, and offers to back it up to a private GitHub repository.
Start here
Run this in your knowledge folder:
/secondbrainos:agent_productivity_claude_code_coach
It will ask where your progress folder should live, whether you want a weekly or monthly strategy cadence, and what time you usually shut down. Then it installs the pieces that make the rest automatic.
Setup has four parts. Three are required: progress tracking, remote access to your Mac from a second device (your phone counts), and Todoist. One is offered and yours to decline: a private GitHub repository for your knowledge folder. Nothing else depends on it. Allow about two hours, and let it finish before asking it for anything else — every other skill reads what setup writes. Three guides, in order: progress tracking and GitHub, then remote access, then Todoist and your first week.
What you can do with it
Your day gets written up without you asking. When you close a Claude Code session, a hook writes that day's progress file: your commits and your logged activity merged into named themes rather than two separate lists, with commit hashes inline and a three-line footer. Several sessions in one day each refresh the same file with a fuller picture.
Your week gets a skim layer. Ask for a weekly recap and it reads the seven daily files locally through QMD — no cloud, no re-reading your activity log — and gives you Shipped, In progress, Dropped, a named pattern for the week, and three to five things to carry forward. It asks you one question first: what dragged this week. Your answer leads; the files are evidence.
Your month gets a retro that names your patterns. The monthly recap builds from the weekly ones, asks you what moved the needle, what dragged, and what you will stop, then names the two to four patterns your own files actually show. It also scores last month's carry-forward list: done, partly, or not touched. Those patterns become the yardstick — later, when you add a task outside the weekly batch, the agent checks it against them and tells you in one line whether it fits.
Your strategy comes out as a document you can send. On your cadence it turns the latest recap into one file: Focus, Bets, Not doing, Numbers to watch, Tasks. Then it exports a clean, self-contained HTML next to the markdown in the same step, using one fixed stylesheet — it prints well and works in dark mode. No slide decks, and PDF only if you ask.
Your week's tasks land in Todoist. It takes the Tasks section from that strategy file, checks what you already have open, and reconciles the two with you before writing anything: what to create, what to carry over with a new date, what to drop. New tasks get spread across the working week rather than dumped on Monday, and each task's Todoist id is written back into the strategy file so the two stay connected.
Your Mac answers from anywhere you are. A private tunnel between your own devices, so the Mac stays invisible to the internet, and a session that lives on the Mac whether you are connected or not. The wifi drops, the iPad locks, and you come back to the words you typed but had not sent. Setup is not declared done until you have proved it from the second device, including a push to GitHub from there if you connected it.
A few things worth knowing early
The daily recap fires when a session ends, not at a set time. This is deliberate. A scheduled 11:59pm job silently never runs when the lid is down or the Mac is asleep, which is most nights. Two guards keep it honest: a session where you typed nothing is skipped rather than recapped, and the recap's own headless session cannot trigger another recap. You can check both in .trigger-probe.log inside your progress folder.
Two setup steps are shared with the Knowledge Work Coach, and get skipped if you have them. The hooks, the utility scripts and the QMD plugin come from the same first-time setup. If you already ran the Coach, most of that step is skips — that is the correct outcome, not a failure.
Once setup is done, it writes to exactly two places: your progress folder and Todoist. Not your notes, not cloud knowledge. If you want to capture a note, that is the Knowledge Work Coach. This separation is what keeps the record trustworthy.
The automatic backup covers one thing: the day's progress file. When a session closes, that file is committed as Daily progress — YYYY-MM-DD and, if you connected GitHub, pushed to your private repository. If you did not, the commit stays on your Mac and nothing leaves it. Nothing else is ever staged. Your notes and everything else in the folder go to GitHub when you commit them, or ask the agent to. .daily-recap.log in your progress folder shows what happened each time.
Files are laid out by month and ISO week — YYYY-MM-Month/week-NN/ — with daily files, weekly recaps and weekly strategies inside the week folder, and monthly recaps at month level. A week spanning two months appears in both, with each day filed under its own date.
What this does not do
It does not capture notes, write your CLAUDE.md, or build custom skills. It does not set up GitHub Actions runners or PR workflows. And it will not run a recap or a strategy unasked; it offers in one line at the right moment and waits.
If you get stuck, reply to this email. It reaches me.