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

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

At a glanceExport risk by user rolePermission boundaries found in the bulk-export PRD
ItemRole actionRisk
ViewerTrigger ExportNone (read-only access)
EditorDelete Source DataRace condition during export
AdminChange Export FormatCould break legacy integrations

Example for: a new bulk-export feature for a cloud accounting platform. ## 1. Silent Failure Modes - Export process times out on large datasets without triggering a notification. - Partial data exports occur if the connection drops, leaving the user with an incomplete file but no error flag. - Background job queue saturation prevents the user from receiving a completion email. ## 2. Permission Boundaries | Role | Action | Risk |
| --- | --- | --- |
| Viewer | Trigger Export | None (read-only access) |
| Editor | Delete Source Data | Potential race condition during export |
| Admin | Change Export Format | Could break legacy integrations | ## 3. Data Migration and State Risks 1. Current schema lacks a 'last_exported_at' timestamp, making incremental exports impossible without a migration. 2. Changing the CSV delimiter setting mid-export could cause row corruption. 3. Large exports may exceed memory limits on the primary read-replica if not throttled. ## 4. Explicitly Excluded Edge Cases - Support for encrypted PDF exports (out of scope for v1). - Automated scheduling of recurring exports (out of scope for v1). - Direct API integration with third-party cloud storage providers (out of scope). This is not legal or technical architectural advice; consult your engineering lead for final implementation.

Written by AI from this prompt. Your results will vary.

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.

Keep exploring

More in Product Management
Product Management

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.