Spec Review
Catch weak requirements before they become weak designs
Reviews product specs for completeness, clarity, and agent-readiness. Scores each section against specific criteria, flags vague requirements, checks that success criteria are evaluable by an agent, and outputs a structured verdict with prioritized fixes. The quality gate between requirements and design.
How it works
Point it at a spec
Select a product spec from your project. The agent loads the spec, research briefs, personas, and any related artifacts for full context.
Section-by-section evaluation
Each section is scored 1-5 against specific criteria: are requirements testable? Are success criteria agent-evaluable? Are edge cases covered? Vague language is flagged with concrete replacements.
Verdict with prioritized fixes
Get a clear rating — Ready, Needs Work, or Not Ready — with scored sections and prioritized findings. Fix the issues, re-review, and advance to design spec.
Point it at a spec
Select a product spec from your project. The agent loads the spec, research briefs, personas, and any related artifacts for full context.
Section-by-section evaluation
Each section is scored 1-5 against specific criteria: are requirements testable? Are success criteria agent-evaluable? Are edge cases covered? Vague language is flagged with concrete replacements.
Verdict with prioritized fixes
Get a clear rating — Ready, Needs Work, or Not Ready — with scored sections and prioritized findings. Fix the issues, re-review, and advance to design spec.
Why use Spec Review
Catch gaps early
Identifies missing sections, untestable requirements, and weak success criteria before they propagate into design and prototyping.
Agent-evaluable success criteria
Ensures every success criterion can be verified by an agent reviewing a prototype — closing the loop from spec to design review.
Ambiguity detection
Flags vague words like "intuitive", "gracefully", and "as needed" with specific, testable replacement suggestions.
Structured scoring
Section-by-section scores (1-5) make it clear exactly where the spec is strong and where it needs work — no guessing.
When to use Spec Review
Pre-design quality gate
You have a product spec and want to verify it's solid before feeding it into design spec and prototyping.
We just wrote the product spec for the new onboarding flow. Review it before I hand it off to design — make sure the success criteria are tight enough to evaluate later.
Spec iteration
A spec has been updated after feedback and you want to confirm the fixes actually addressed the issues.
I updated the price alerts spec based on your last review. Check if the success criteria and edge case coverage are good now.
Inherited spec audit
You're picking up a spec someone else wrote and need to assess its quality before building on it.
This spec was written last month. Review it — I need to know if it's ready for design or if we need to fill in gaps first.
More from your Product Manager
See Spec Review in action
See how Spec Review catches weak requirements before they become weak designs.