Who this is for
Founders and PMs who spot bugs while using their own product and need them logged before the next thing steals their attention.
The moment this saves you
I hit a bug mid-demo, mutter “ugh, that’s broken,” and by the time I open the tracker the exact repro is gone, all I’ve got left is one vague sentence engineering has to chase me about.
See it work
Messy spoken thought in. A clean, structured artifact out.
Okay so I'm on the billing page and I clicked upgrade and it just spun forever, like the button went into a loading state and never came back. I was on Safari, the new one, and I was already logged in as a paid user weirdly. Oh and also separate thing, the avatar in the top right is showing the wrong initials, it's showing my old name. Anyway the upgrade thing is the bad one, that's blocking people from paying us.
Bug 1, Upgrade button hangs in loading state on billing page
- Severity: High (blocks payment)
- Steps to reproduce:
1. Log in as an existing paid user 2. Open the billing page 3. Click "Upgrade"
- Expected: Upgrade flow proceeds
- Actual: Button enters loading state and never resolves
- Environment: Safari (latest)
Bug 2, Avatar shows wrong initials
- Severity: Low
- Steps to reproduce:
1. View the top-right avatar
- Expected: Current account initials
- Actual: Shows initials from a previous name
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 a bug (or a few) I just noticed in our product. Turn what I say into a structured bug report. For each distinct bug, output a block with: a bold one-line Title, Severity (infer Low/Medium/High from how blocking it sounds), numbered Steps to Reproduce, Expected, Actual, and Environment (only if I mention a browser, device, OS, or account state). Keep my real technical details, drop my filler words and false starts. If I describe more than one bug, output one separate block per bug, most blocking first. Only include fields I actually gave you, never invent steps, severity rationale, or environment I didn't mention. Output only the bug report(s), no preamble, no 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 click copies it and shows you exactly how to drop it into Contextli.
Next, open Contextli, go to the Contexts page, click Import, choose From JSON, paste, then Import Context. It is ready to use.
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
Feature Idea Capture
The idea lands halfway through your walk and it's gone in ninety seconds. Say 'Hey Siri, dictate with Contextli' and think out loud. By the time you're back at your desk, the insight AND the why are waiting for you.
Standup Update
Standup's in two minutes and you're still reconstructing yesterday. Skip the typing. Talk through your day in whatever order it comes out, and get a clean yesterday, today, and blockers post you can drop straight in the thread.
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.
Questions people ask
Questions founders ask about Product Bug Report
What should a bug report include?
A good bug report includes a clear title, steps to reproduce the issue, the expected behavior, the actual behavior observed, the severity or priority, and the environment details such as OS, browser, and app version. The Product Bug Report context structures your spoken description into these fields automatically, so nothing gets left out when you are in the middle of debugging.
How do I write a bug report in under a minute?
Speak what you found: describe the issue, what you expected, what actually happened, and how bad it is. The Product Bug Report context structures your words into a complete bug report you can paste directly into Jira, Linear, or GitHub Issues. Most take under 60 seconds to dictate, so you capture them without breaking your flow.
How do developers capture issues without interrupting their flow?
The key is to capture the issue immediately without switching context mentally. Contextli lets you speak a quick voice note describing it and produces a bug report from it. You can dictate while the issue is still on screen, then paste the formatted output into Jira, Linear, or GitHub Issues when you come up for air. No typing is required during the capture step.
Can I write a bug report by talking instead of typing?
Yes. The Product Bug Report context lets you speak a description in plain language and converts it into a structured bug report with all the required fields filled. You speak the way you would explain it to a colleague, and the context handles the formatting.
How do I add this context to Contextli?
Copy the context on this page, then open Contextli and go to the Contexts page. Click Import, choose From JSON, paste it into the Import from Clipboard window, and click Import Context. It is ready to use in under 30 seconds. If you do not have Contextli yet, you can download it for free first.
Is my voice recording private? Does Contextli send it anywhere?
Your voice recording and the transcription are stored on your device only. Contextli processes your audio locally and does not send your recordings or transcription text to any server. The structured output it produces is text you control, and you decide where it goes.
Can I change what the output looks like?
Yes. Every context in Contextli is a starting point you can edit. Open the context in the app, change the instructions to adjust the structure, tone, or fields, and save. The next time you use it, the output reflects your changes. You are not locked into the default format.
Do I need to install an app to use this context?
Yes. Contextli is a free app. Download it, then copy this context and paste it into the Import from Clipboard window on the Contexts page. The whole process takes about 30 seconds.