review-specifications

Audit technical specifications and produce a structured findings report.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill review-specifications
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-specifications
Source: https://github.com/tomzx/agents/tree/main/skills/review-specifications
Command: npx skills add https://github.com/tomzx/agents --skill review-specifications

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits a technical specification and reports findings across six categories: ambiguities, inconsistencies, incoherences, missing information, implementability, and reversibility.

Core Features & Use Cases

  • Ambiguities: identifies unclear terms, ambiguous requirements, and inconsistent state transitions.
  • Inconsistencies: checks data models, API contracts, and progress flows for mismatches.
  • Incoherences: detects conflicting architectural decisions and contradictory statements.
  • Missing Information: flags gaps in requirements, interfaces, non-functional requirements.
  • Implementability: assesses practicality, dependencies, risks, and constraints.
  • Reversibility: evaluates ability to rollback changes and data migrations.
  • Use Case: When reviewing a feature spec, API contract, or requirements doc, generate a structured findings report, a prioritized list of questions, and a plan for closure.

Quick Start

Provide the target specification document and run the review to produce a findings report.

Frequently Asked Questions about review-specifications

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

FAQPage Schema
How do I audit technical specifications for ambiguities and missing information?▼

To audit technical specifications for ambiguities and missing information, provide the specification document to trigger a structured review that identifies unclear terms, inconsistent state transitions, and gaps in requirements or interfaces.

What is the best way to review an API contract for inconsistencies and implementability risks?▼

Reviewing an API contract for inconsistencies and implementability risks involves checking data models and progress flows for mismatches, then assessing practical constraints and dependencies to produce a prioritized findings report.

How do I check a feature specification for reversibility and rollback concerns?▼

Checking a feature specification for reversibility evaluates the ability to rollback changes and data migrations, flagging potential issues where reversing a deployed feature or migrating data back is impractical.

Can I use this to generate a prioritized list of questions for a formal SDLC requirements review?▼

Yes, you can use this to generate a prioritized list of questions for a formal SDLC requirements review by processing the specification document to output unresolved questions and a suggested plan for closure.

What types of incoherences are detected during a technical specification audit?▼

A technical specification audit detects incoherences by identifying conflicting architectural decisions and contradictory statements within the document, ensuring structural alignment across the described system behavior.

Do I need to provide requirements documents alongside the specification to get a full findings report?▼

You do not need to provide requirements documents to get a findings report, as the specification document is sufficient, but supplying optional requirements enhances the audit by contextualizing the expected feature scope.