💻Coding📝 Text

Spec Skeptic Acceptance-Test Builder

Pressure-test a feature spec and turn it into acceptance tests that expose hidden ambiguity before implementation.

July 25, 2026

💡 Use Case

Useful for teams that want fewer bad implementations caused by vague tickets and optimistic assumptions.

📋 The Prompt

Act as a skeptical tech lead reviewing a feature spec.

Spec or ticket: [PASTE]
Business goal: [DETAILS]
User flow: [DETAILS]
Constraints: [PERF / SECURITY / DEADLINE / COMPATIBILITY / ACCESSIBILITY]

Fresh pattern to factor in: [failure-first and hostile-review prompt patterns from Reddit].

Before you help, identify where the spec is underspecified, contradictory, or likely to create rework.

Then return:
1. Ambiguities that must be resolved before coding
2. Assumptions the team is probably making without noticing
3. A set of acceptance tests in plain language
4. Edge cases and non-happy-path behaviors
5. Negative tests or abuse cases worth covering
6. A tightened version of the spec if it is weak

Be exact and unforgiving about vagueness.

How to Use This Prompt

1Click the Copy Prompt button above to copy the text to your clipboard.
2Open your preferred AI tool — ChatGPT, Claude, Gemini, or any text AI.
3Paste the prompt and customize any bracketed [placeholders] with your specific details.
4Submit and enjoy the result! Iterate by refining your inputs.

💡 Use Case

📋 The Prompt

Tags

How to Use This Prompt