Spec review before build
OfficialOfficial · updated Nov 4, 2026 · v1.0.1
Reviews a PRD or spec before build for ambiguity, missing empty/loading/error/permission states, metrics, rollout, and a first-time user walk-through.
Sign up free to add this skill to your pod
You come back here after you sign in, and add it with one click.
When to use it
- A PRD or spec is about to go to engineering for estimates
- A feature shipped with surprises and the next spec needs a harder look
What you give it
- The spec or PRD text
- Target user (optional)
- Deadline and team (optional)
What you get
A verdict, a first-time user walk-through, blocking and should-fix findings with quotes, a states table, and metric and rollout checks.
Changelog
- v1.0.1 · Nov 4, 2026 · Example: S1's "3 clicks or fewer" is marked [our suggestion], as the checks require for defaults the review proposes.
- v1.0.0 · Nov 4, 2026 · First release.
Sources
- Designing Empty States in Complex Applications: 3 Guidelines - NN/G (2026-11-04)
- Error-Message Guidelines - NN/G (2026-11-04)
- Feature Toggles (aka Feature Flags) (Martin Fowler) (2026-11-04)
Related skills
- PRD from messy notes Turns notes, Slack threads, and call notes into a PRD: problem with evidence, goals and non-goals, metrics, must/should/could requirements, and flagged gaps.
- User stories with acceptance criteria Turns a feature into user stories with Given/When/Then acceptance criteria, edge cases, out-of-scope notes, and an INVEST check per story.
- A/B test plan Writes an A/B test brief: hypothesis, primary and guardrail metrics, MDE, sample size and duration with the math, stop rules, and a decision rule set in advance.
- Decision record (decision log entry) Records a decision as a short log entry: the decision, context, options considered, why, who decided, the date, status, and a revisit trigger.