eo-spec-review

Review module specifications against seven dimensions and generate a prioritized spec-review.md report.

30|5|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/SimpleEve/eo-skills --skill eo-spec-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eo-spec-review
Source: https://github.com/SimpleEve/eo-skills/tree/main/eo-spec-review
Command: npx skills add https://github.com/SimpleEve/eo-skills --skill eo-spec-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many development teams create module specifications that lack completeness, contain ambiguities, or miss critical constraints, leading to confusion during planning and implementation.

Core Features & Use Cases

  • Systematically checks spec structure against a template and seven review dimensions.
  • Detects ambiguous language, missing requirements, and inconsistencies across modules.
  • Generates a detailed spec-review.md report with prioritized issues (P0, P1, P2) and updates the module index.

Quick Start

Run the eo-spec-review skill on a module to produce a structured spec review report.

Frequently Asked Questions about eo-spec-review

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

FAQPage Schema
How do I review module specifications for missing requirements and ambiguities?▼

To review module specifications for ambiguities, you can systematically parse spec templates against seven review dimensions to detect missing requirements and generate a structured report with prioritized findings.

What is the best way to validate that a spec is clear and implementable before development?▼

Validating spec implementability involves checking the document structure against a template, detecting ambiguous language, and outputting a detailed report with prioritized issues (P0, P1, P2) to resolve gaps before development.

When should I run a spec review during the development workflow?▼

You should run a spec review during module initialization or after major spec changes. This timing ensures requirements remain clear, complete, and implementable before downstream planning and implementation phases begin.

How do I generate a structured QA report for module documentation?▼

You can generate a structured QA report for module documentation by evaluating the spec against seven review dimensions, which outputs findings with priority levels into a spec-review.md file and updates the module index.

Does spec review work without integrating external QA frameworks or dependencies?▼

Yes, spec review operates independently without external dependencies. It internally parses spec templates and evaluates review dimensions to produce a standalone spec-review.md report with prioritized issues.

What types of inconsistencies across modules should a spec review detect?▼

A spec review should detect missing requirements, ambiguous language, and structural inconsistencies across modules. It evaluates completeness against seven review dimensions and reports findings with P0, P1, and P2 priority levels.