Sprint Closeout Notes, Written for You
For the last afternoon of the sprint. DuckyHelper pulls what's done in Linear and what merged in GitHub, notes what's carrying over and why, picks out the wins, and writes the closeout in your sprint folder.
“Write the sprint closeout in Notion from done Linear issues and merged GitHub PRs, with carryover and wins.”
- 01Turn Linear and GitHub into APIs it can callIt watches each site's own requests once and saves them as actions. Kept on your device.
listIssues(cycle, state)searchPulls(query)
- 02Pull the sprint's done issues
- 03Pull PRs merged in the same window
- 04Find the carryover and what blocked it
- 05Pick two or three wins
- 06Write the notes in Notion
You getEvery sprint, written up. A clear record of what shipped, what didn't and why. The next closeout is one ask.
A run, drawn from this page · early access on Mac
Nothing to send, so it runs straight through.
Nothing in this job sends a message or pays for anything, so it works through to the end and tells you when it's done. If a step ever would, it's built to stop and ask you first.
If it hits a sign-in, you sign in yourself. It's built not to type your passwords or card numbers.
Do it once. Then let it repeat.
When it's done, it offers to keep doing it: every Monday at 9:00 AM. Each run goes through the API it learned the first time, so it's quick, and it's still built to ask before it sends or pays.
Always-on automations are in early access on Mac.
Before you ask it.
What do I say?
Press fn (Ctrl+Shift+Space on Windows and Linux) and ask out loud, in your own words, like "Write the sprint closeout in Notion from done Linear issues and merged GitHub PRs, with carryover and wins."
Why is the second time faster?
The first time, it writes small JavaScript tools for Linear, GitHub and Notion and builds an API from each site's own buttons, forms and requests. After that it calls them directly, so the job runs in one go instead of click by click. It costs less and breaks less.
Will it send anything without me?
It's built to ask first before it sends a message or pays for anything, and to wait for your yes. It may not recognize every send or payment, so keep an eye on tasks that involve messages or money. It's built not to type your passwords or card numbers: you sign in yourself, and it picks up from there.
Why not just do it by hand?
Closeout notes mean cross-checking issues and pull requests, and they're always written from memory.
Can it keep doing this on its own?
Yes. When it's done it offers to make it automatic (every Monday at 9:00 AM). Each run goes the same way and is still built to ask before it sends or pays.
Can I use this today?
Doing jobs in your apps is in early access on Mac. Talking to DuckyHelper, and having it see your screen and draw on it, works today on Mac, Windows and Linux.
- Early access
“Deploy the latest commit on main to production and tell me when it's live.”
Ship the Latest Commit and Watch the Build
See it run
- Early access
“Signups are failing in production. Check the Vercel logs, reproduce it, and open a PR with a fix.”
Debug a Vercel App From Logs to Fix
See it run
- Early access
“Check my Supabase project's health: schema, row security and anything that looks off.”
Check Your Supabase Database Is Healthy
See it run
Do anything
Ask it a question or hand it a job, in any app.
Doing jobs for you is in early access on Mac. Asking works on Mac, Windows and Linux.