Who this is for
Developers on async teams who have to post a written standup but think faster than they type.
The moment this saves you
Standup’s in two minutes and I’m staring at the thread trying to reconstruct yesterday, sand off the rambly bits, and make three bullet points sound coherent.
See it work
Messy spoken thought in. A clean, structured artifact out.
Yesterday I was mostly heads down on the auth refactor, got the token rotation working finally, that took way longer than expected because the test suite was flaky. I also reviewed Priya's PR on the export thing. Today I want to wire the rotation into the actual login flow and hopefully start on the rate limiting. The one blocker is I'm waiting on the staging database creds from infra, can't really test the rotation end to end without them.
Yesterday
- Got token rotation working on the auth refactor (slowed by a flaky test suite)
- Reviewed Priya's export PR
Today
- Wire token rotation into the login flow
- Start on rate limiting (stretch)
Blockers
- Waiting on staging database creds from infra, can't test rotation end-to-end without them
The workflow
Record a voice note
Hit the hotkey and talk, no formatting, no typing.
Tag it with this context
Contextli shapes your words into the structured output above.
Find it later
Everything's searchable and organised by context.
Pull it into Claude or ChatGPT
Bring your contexts straight into your AI tools with the Contextli MCP.
Your raw recording and transcription stay on your device, so you can always go back to the original.
The prompt behind this context
I'm going to talk through my work day out loud, probably out of order. Turn it into a written standup with exactly three bold sections: **Yesterday**, **Today**, and **Blockers**. Put each thing I did under Yesterday, each thing I plan to do under Today, and anything I'm waiting on or stuck behind under Blockers. Use short bullet points, keep the substance and any names or ticket references, drop filler and hedging. If a section has nothing, write "- None" under it rather than omitting it. Don't invent tasks or blockers I didn't mention. Output only the three sections, no greeting or sign-off.
Make it your own. This is a starting point. Once it's in Contextli, tweak the instructions so the output comes out exactly how you like it.
Use this context
One tap adds it to your clipboard. Open Contextli and paste to add it.
Next, open Contextli, Contexts, Import, paste.
Make it your own. This is a starting point. Once it's in Contextli, tweak the instructions so the output comes out exactly how you like it.
Your raw recording and transcription stay on your device, so you can always go back to the original.
Related contexts
Code Decision Log
Right after you make the call, while the tradeoffs are still fresh, talk through why you went this way and what you rejected. Three months from now when someone asks 'why a queue here?', the answer is already written down.
Product Bug Report
You just watched something break mid-demo. Don't lose the repro hunting for the tracker. Mutter what happened, what you clicked, what you expected, and walk away with a report engineering can actually act on.
Post-Call Debrief
You hang up and the next call's already ringing. Take twenty seconds to debrief out loud while it's fresh, the real objection, the budget hint, who actually decides, and it lands as a CRM note with next steps, not a vague one-liner.