spec-review

Analyze specification documents for completeness and readiness before approval.

1|Updated Feb 10, 2026
One-click install
npx skills add https://github.com/opsMachine/OM-Agency --skill spec-review-opsmachine
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-review
Source: https://github.com/opsMachine/OM-Agency/tree/main/skills/spec-review
Command: npx skills add https://github.com/opsMachine/OM-Agency --skill spec-review-opsmachine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews a specification document to confirm it is complete, unambiguous, and ready for implementation, preventing downstream rework.

Core Features & Use Cases

  • Structured review checklist that validates problem statements, acceptance criteria, non-goals, assumptions, constraints, and security considerations.
  • Guidance for identifying gaps, risks, and actionable improvements to ensure readiness before development.
  • Use cases include post-interview spec validation, pre-implementation reviews, and quick readiness checks when someone asks "is this ready?".

Quick Start

Provide the path to the spec document you want reviewed.

Frequently Asked Questions about spec-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate a specification document before implementation?

To validate a specification document before implementation, provide the spec file path to the review tool. It analyzes problem statements, acceptance criteria, and constraints to produce a readiness assessment with stated gaps.

What is the best way to check if product requirements are ready for development?

Checking if product requirements are ready for development involves running the specification through a structured review checklist. This process evaluates non-goals, assumptions, and security considerations to prevent downstream rework.

How do I review acceptance criteria and non-goals for completeness?

Reviewing acceptance criteria and non-goals for completeness requires evaluating the specification against a structured checklist. This identifies gaps, risks, and actionable improvements to ensure total readiness before coding begins.

Can I use a spec review checklist for post-interview validation?

Yes, you can use a spec review checklist for post-interview validation. The process evaluates problem statements and open questions to confirm the captured requirements are complete, unambiguous, and ready for implementation.

What should a pre-implementation requirements review cover to prevent rework?

A pre-implementation requirements review should cover problem statements, acceptance criteria, non-goals, assumptions, constraints, security considerations, and open questions. This ensures the specification is unambiguous and prevents downstream rework.

How do I identify gaps and risks in a product specification?

Identifying gaps and risks in a product specification requires analyzing the document against a structured review checklist. This process highlights missing assumptions, constraints, and open questions to produce a clear readiness assessment.