Who this is for
PMs and founders fielding feature requests who want the underlying problem captured, not just the literal feature a user happened to ask for.
The moment this saves you
A user asks for a button, I log 'add a button,' and three months later we build the literal button instead of solving the actual problem they had, because the why never made it into the ticket.
See it work
Messy spoken thought in. A clean, structured artifact out.
Feature request from a customer call. The account manager at Brightline asked if we could add a way to bulk-edit tags. But digging in, the real problem is they have like 5000 contacts mistagged from a bad import, and they're editing them one by one which is brutal. So the request is bulk tag editing but the problem is really cleanup after a messy import. This is the third customer to hit this. Probably medium-large effort. The workaround they're using now is a spreadsheet export and reimport which is awful.
Feature request: Bulk-edit tags
- Requested by: Account manager at Brightline (3rd customer to ask)
- Literal ask: A way to bulk-edit tags
- Real problem: ~5,000 contacts mistagged from a bad import, currently fixed one by one
- Current workaround: Spreadsheet export and reimport (painful)
- Rough effort: Medium-large
- Note: The deeper need is cleanup after a messy import, not just bulk editing
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 describe a feature request from a user or customer. Turn it into a structured feature brief: a bold Title (the requested feature), then labeled lines: Requested by (who, and how many have asked if I say), Literal ask (what they literally requested), Real problem (the underlying need, which is the point of the brief), Current workaround (only if mentioned), Rough effort (only if I estimate), and Note (any deeper insight I add). Separate the literal ask from the real problem clearly. Don't invent customers, counts, or effort. If I describe more than one request, make one brief each. Output only the brief(s).
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
Product Demo Feedback
You watch a user try your product and see exactly where it breaks down, then the meeting moves on and the insight gets diluted. Speak what you observed right after. You keep the raw signal, the confusion, the workaround, the delight, so the team fixes the real thing.
User Research Observation
Right after a user interview, your memory starts smoothing the awkward truths into what you hoped to hear. Speak it now, what they actually said and did, where they got stuck. You get a clean observation note that keeps the real signal, not your wishful version of it.
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.
Questions people ask
Questions product managers ask about Feature Request
What should a feature request include?
A good feature request 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 Feature Request 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 feature request in under a minute?
Speak what you found: describe the issue, what you expected, what actually happened, and how bad it is. The Feature Request context structures your words into a complete feature request 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 feature request 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 feature request by talking instead of typing?
Yes. The Feature Request context lets you speak a description in plain language and converts it into a structured feature request 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.