Stress Test Your Product Requirements Document for Edge Cases
This prompt audits your feature PRD to identify hidden technical risks, permission gaps, and scope creep before development begins.
Prompt
Act as a Senior Staff Engineer. I will provide a PRD for a new feature. Your job is to audit it for technical risks and scope creep. First, ask me these 3 questions: 1. What is the primary user goal of this feature? 2. Is this feature replacing an existing workflow? 3. What is the most critical technical constraint or dependency? Wait for my response, then provide a four-part audit. Rules: 1. Identify silent failure modes where a user might think a task completed but it did not. 2. Define missing permission boundaries for different user roles. 3. List data migration risks or state conflicts with existing database schemas. 4. Explicitly define what edge cases are out of scope to prevent feature bloat. Output format: ## 1. Silent Failure Modes (bulleted list) ## 2. Permission Boundaries (table with columns: Role, Action, Risk) ## 3. Data Migration and State Risks (numbered list) ## 4. Explicitly Excluded Edge Cases (short list) This is not legal or technical architectural advice; consult your engineering lead for final implementation. Wait for my answers to the 3 questions before starting.Example output
Tips and common edits
Why this works
- Forces the model to identify specific failure modes rather than generic feedback.
- The table format for permissions makes security gaps instantly visible.
- Explicitly excluding edge cases prevents the common pitfall of scope creep.
Use this prompt when you have a near-final PRD draft and want a technical gut check. Copy the prompt into ChatGPT, Claude, or Gemini. Paste your PRD text when the model finishes asking the three questions.
Common edits
- Add a specific technical stack name like AWS or Postgres to the prompt for more targeted risk analysis.
- Ask the model to prioritize risks by impact level if your PRD is particularly complex.
Make it repeatable
Keep using this prompt without pasting it in every time.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Define Feature Non-Goals and Scope Boundaries
Sort requested features into three clear out-of-scope buckets with explicit business reasons to prevent scope creep.
Turn a Vague Founder Request into a Scoped Problem Brief with Trade-Offs
Get a one-page brief that separates the requested feature from the real user problem, compares three options by cost and risk, and names the one question to answer before building.
Write a One-Page PRD for a Small Feature That Engineers Can Start From
Get a one-page PRD under 400 words with one problem statement, one primary KPI, testable requirements, explicit non-goals and an owned open-questions list.
Perform a Pre-Mortem Analysis for Product Launches
Generate a detailed risk assessment by imagining your product launch failed six months from now, categorized by adoption, infrastructure, and team capacity.
Write a Product Requirements Document from Your Raw Feature Notes
Turns pasted feature notes into a PRD where each requirement has numbered, testable acceptance criteria and missing details become open questions.
Define beta cohorts and launch exit metrics
Build a structured cohort plan and clear release criteria for your upcoming beta launch. Use this to prevent feature creep and ambiguous testing timelines.
- Turn onboarding test notes into root causes
- Decline a stakeholder feature request diplomatically
- Draft a working-backwards press release and FAQ
- Translate technical debt into business risk and ROI
- Audit Your Signup-to-Activation Flow and Find the Steps to Cut First
- Create a Feature Deprecation and Sunset Migration Plan