Code prompts
Code prompt

Audit a spec for hidden assumptions before handing it to an agent

You have a spec, build plan, or design doc and want to find the gaps before an AI agent or junior engineer takes everything literally and fills them with guesses.

Works best in: Claude

Audit this spec for hidden assumptions, ambiguities, missing edge cases, and contradictions — before it's handed to an AI agent or junior engineer who will take everything literally and fill any gap with their own guess.

Spec:
```
{{paste the spec / build plan / design doc}}
```

What it's for: {{kind of project, who/what will execute it}}

For each issue:
- **Type**: hidden assumption | ambiguity | missing edge case | contradiction | underspecified interface
- **Severity**: blocker | will-cause-rework | nice-to-fix
- **Location**: quote the exact phrase or section
- **The problem**: what an executor would do wrong, concretely
- **Patch**: a one-sentence rewrite or addition

Group issues by severity. End with **Top 3 to fix before building**.

Skip stylistic issues and general improvement suggestions. Only flag things that will cause a wrong build or wasted work. If a section is genuinely tight, say so — don't manufacture issues to fill the list.
·Open in·Share
spec reviewplanningagents

More code prompts

All code prompts

Go deeper