spec-review

Compare code implementation against task specification for completeness and precision.

25|7|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/xoai/sage --skill spec-review-xoai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-review
Source: https://github.com/xoai/sage/tree/main/core/capabilities/review/spec-review
Command: npx skills add https://github.com/xoai/sage --skill spec-review-xoai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that implemented code precisely matches its intended specification, preventing scope creep and ensuring all requirements are met.

Core Features & Use Cases

  • Completeness Check: Verifies that all specified requirements have been implemented.
  • Precision Check: Confirms that no unrequested features or code have been added.
  • Use Case: After a developer implements a new feature, this Skill acts as an automated quality gate to confirm the code adheres strictly to the initial task description before further testing or deployment.

Quick Start

Use the spec-review skill to verify the implementation against the task specification.

Frequently Asked Questions about spec-review

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

FAQPage Schema
How do I verify code against a specification to ensure completeness?

Verifying code against a specification requires an adversarial review process that independently reads the task description and implementation to perform a checklist comparison, identifying missing requirements and ensuring completeness.

What is an automated quality gate for checking code compliance and scope creep?

An automated quality gate for code compliance performs a precision check after feature implementation, scanning for unrequested features to prevent scope creep before further testing or deployment stages.

How do I check for unrequested features in a code review?

Checking for unrequested features involves comparing the actual code against the initial task description to confirm no extra code has been added, ensuring the implementation strictly adheres to the specified scope.

When do I need an adversarial review for my software development workflow?

An adversarial review is needed when implementing a new feature requires strict compliance with a task specification, acting as a verification step to confirm code adherence before moving to deployment.

Can I use spec review for compliance checks without external dependencies?

Yes, you can perform compliance checks without external dependencies by using internal references to independently evaluate the task specification and code, generating a checklist of missing or extra implementation details.