Deconstructing Requirements & Finding Edge Cases
Prompt detail
Act as a meticulous QA lead and a product manager. I've been given a vague requirement from my PM: 'Users should be able to export their project data.' To help me fully understand the scope before I write any code, please help me deconstruct this requirement by:
1. Listing all the clarifying questions I should ask.
2. Identifying at least 5 potential edge cases I need to handle.
3. Suggesting a clear, unambiguous rewrite of the original requirement.
What the prompt does
Vague requirements like "users should be able to export their data" leave engineers guessing about scope, formats, permissions, and failure modes. This prompt transforms an ambiguous one-liner into a structured breakdown: clarifying questions to ask your PM, edge cases that could derail development, and a rewritten requirement that leaves no room for misinterpretation.
With remio, you paste the requirement and instantly receive a comprehensive analysis. remio can reference past Slack threads, meeting notes, and product docs where the feature was discussed, giving you additional context to refine the spec before a single line of code is written.
When to use
• You've received a one-sentence feature request in Slack and need to scope it properly before sprint planning.
• A PM's ticket description is ambiguous, and you want a structured list of questions to bring to the next grooming session.
• You're writing a technical design document and need to enumerate edge cases for a feature that hasn't been fully specified.
• You're onboarding to a new team and want to stress-test requirements you inherited from a previous engineer.
• A stakeholder request changed mid-sprint and you need to quickly reassess scope and identify new unknowns.
Prompt examples
Input: Act as a meticulous QA lead and a product manager. I've been given a vague requirement from my PM: 'Users should be able to export their project data.' To help me fully understand the scope before I write any code, please help me deconstruct this requirement by:
1. Listing all the clarifying questions I should ask.
2. Identifying at least 5 potential edge cases I need to handle.
3. Suggesting a clear, unambiguous rewrite of the original requirement.
remio responds:
Here are 12 clarifying questions to bring to your PM, including: What formats should be supported (CSV, JSON, PDF)? Should exports include archived or deleted items? Are there file size limits or row caps? Is this available to all plan tiers or only paid users? For edge cases, consider: a project with 500K+ rows timing out, a user exporting while another user is actively editing, special characters breaking CSV formatting, an export triggered by a user whose permissions are revoked mid-process, and empty projects generating zero-byte files. A clearer rewrite: "Authenticated users on Pro plans and above can export all non-deleted project data as CSV or JSON files up to 100MB, with a progress indicator and email notification upon completion."
Tip 1: Replace the generic export example with your actual PM's requirement verbatim — the more specific the input, the more targeted the clarifying questions and edge cases will be.
Tip 2: Ask remio to search your recent Slack conversations or meeting transcripts with your PM for additional context on the feature, then feed those details into the prompt for a sharper breakdown.
Tip 3: After generating the output, ask remio to prioritize the edge cases by severity so you can address the most critical ones first in your technical design.
More tips
remio meets all your needs about knowledge
Learn more features
Capture resources from websites, local folders & files.
Get instant, reliable answers from your entire knowledge base.
Your working assistant, on desktop, browser, and mobile.
Unlimited free recording and transcription, no-bot.