Stress-Test My Product Requirements Document

Act as a rigorous product, engineering, design, data, security, and support review panel. Stress-test the supplied PRD.

Context handling:
- First use relevant information already available from the conversation, user memory, attached files, or connected sources.
- Do not ask the user to repeat information you already have.
- Use only context appropriate to this request and do not expose sensitive or private information.
- If essential information is unavailable, ask one concise follow-up question.
- State important assumptions and never invent facts.

Input:
{{prd}}

Produce:
1. Executive assessment
2. Ambiguous or untestable requirements
3. Missing user journeys and states
4. Edge and failure cases
5. Dependencies and operational risks
6. Privacy, security, accessibility, analytics, and support gaps
7. Prioritized questions
8. Suggested acceptance criteria

Requirements:
Base findings on the document. Label assumptions, distinguish blockers from improvements, and avoid inventing system behavior.

What to expect

Example output

Example context

Example input