skills.rest
xiongxianfei
xiongxianfeiCOMMUNITY
Explore all skills by this author →
GitHub

spec-review

Reviews feature specs to identify ambiguities and gaps for testable contracts.

3|Updated Apr 19, 2026
Search Tags:#documentation#requirements#testability#verification#edge-cases#acceptance-criteria#spec-review
One-click install
npx skills add https://github.com/xiongxianfei/rigorloop --skill spec-review-xiongxianfei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-review
Source: https://github.com/xiongxianfei/rigorloop/tree/main/.codex/skills/spec-review
Command: npx skills add https://github.com/xiongxianfei/rigorloop --skill spec-review-xiongxianfei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews a feature spec to uncover ambiguities, gaps, and non-goals so that architecture, test planning, and implementation can proceed with a clear contract.

Core Features & Use Cases

  • Requirement clarity evaluation: ensures each requirement has a single interpretation and traceable acceptance criteria.
  • Normative language validation: checks correct usage of MUST, SHOULD, and MUST NOT and flags vague or aspirational statements.
  • Completeness and testability assessment: verifies edge cases, boundary conditions, permissions, and migration considerations, and maps MUST items to tests.
  • Evidence and traceability: identifies linked proposals, exploration artifacts, and related contracts to ensure coverage and alignment.

Quick Start

Review the provided feature spec and return a precise, testable contract with actionable improvements.

Frequently Asked Questions about spec-review

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

FAQPage Schema
What does reviewing a software specification for testability involve?▼

Reviewing a software specification for testability involves identifying ambiguities and gaps to produce a precise contract. It ensures MUST clauses are verifiable, edge cases are covered, and acceptance criteria are explicit.

How do I validate normative language like MUST and SHOULD in feature specs?▼

Validating normative language in feature specs requires checking correct usage of MUST, SHOULD, and MUST NOT. This process flags vague or aspirational statements to ensure each requirement has a single, traceable interpretation.

How can I ensure completeness and evaluate edge cases in requirements documentation?▼

Ensuring completeness and evaluating edge cases requires assessing boundary conditions, permissions, and migration considerations. This verification maps MUST items directly to tests, ensuring all requirements are fully testable.

What is the best way to clarify ambiguous acceptance criteria before architecture planning?▼

The best way to clarify ambiguous acceptance criteria is to review linked proposals and exploration artifacts. This evaluates requirement clarity and ensures coverage alignment, yielding a precise contract for test planning.

Can I use this spec review approach for linked proposals and exploration artifacts?▼

Yes, you can apply spec review to linked proposals and exploration artifacts. It identifies related contracts to ensure traceability and verifies that completeness and testability are evaluated across all related documents.

Why does my implementation scoping fail when feature specs lack verifiable MUST clauses?▼

Implementation scoping fails when feature specs lack verifiable MUST clauses because requirements have multiple interpretations. Reviewing the spec exposes non-goals and ambiguities, ensuring architecture proceeds with a clear contract.

Related Skills

Explore More Software Engineering Skills→
kmshihab7878kmshihab7878
6

doc-coauthoring

Guides users through structured, iterative co-authoring workflows for collaborative documents.

Community
Advanced
espensevespensev

qa

Validate code changes against the planning contract and run tests.

Community
Advanced
wahidyankfwahidyankf
3

plan-writing-gherkin-criteria

Enforce structured Given-When-Then syntax for testable acceptance criteria.

Community
Intermediate
ArabelaTsoArabelaTso
142

ambiguity-detector

Detect ambiguous language in software requirements and user stories.

Community
Intermediate