reviewing-spec

Convert clear requirements into formal specifications with defined behaviors and contracts.

107|15|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/rhuss/cc-superpowers-sdd --skill reviewing-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reviewing-spec
Source: https://github.com/rhuss/cc-superpowers-sdd/tree/main/skills/reviewing-spec
Command: npx skills add https://github.com/rhuss/cc-superpowers-sdd --skill reviewing-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents costly rework and delays by thoroughly validating the quality of your specifications before implementation begins. It catches ambiguities, gaps, and inconsistencies early, ensuring developers have a clear, implementable blueprint.

Core Features & Use Cases

  • Completeness Check: Verifies all required sections are filled and no placeholders remain.
  • Clarity Assessment: Identifies vague language, ambiguous requirements, and undefined terms.
  • Implementability & Testability: Ensures the spec can be translated into a concrete plan and that its success criteria are measurable.
  • Constitution Alignment: Checks if the spec adheres to project-wide principles and standards.
  • Use Case: After drafting a new feature spec, use this skill to get an objective report on its soundness, highlighting any critical issues that need fixing before you start coding.

Quick Start

To review the spec for the user profile API, simply say: Review the spec at specs/features/user-profile-api.md for soundness.

Frequently Asked Questions about reviewing-spec

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

FAQPage Schema
How do I validate a specification for completeness and clarity before implementation?

Spec validation checks for completeness, clarity, and implementability by identifying missing sections, vague language, undefined terms, and unmeasurable success criteria. Run a soundness review on your spec to catch ambiguities and gaps early, ensuring developers have a clear, executable blueprint before coding begins.

What should a well-formed specification include to be implementable?

A sound specification includes Requirements, Behaviors, Contracts, Error Handling, Success Criteria, Constraints, and User-visible paths. It answers WHAT and WHY without implementation details (HOW), giving developers enough clarity to build and testers enough precision to verify the result.

Why review specs before starting development?

Spec review prevents costly rework and delays by catching inconsistencies, gaps, and ambiguities before implementation. Early validation ensures alignment with project principles, measurable success criteria, and prevents developers from discovering missing requirements mid-build.

How do I know if a specification is testable?

A testable spec has measurable success criteria, defined error cases, and clear user-visible behaviors that can be verified objectively. Spec review validates that success criteria are concrete enough to translate into test cases and that all acceptance conditions are unambiguous.

Can I use spec review for PRDs, tickets, and other requirement sources?

Yes. Spec review applies to detailed, well-defined requirements from any external source—PRDs, tickets, or design documents. It produces formal, executable specifications that meet WHAT/WHY requirements without requiring exploratory dialogue.

What happens if my specification has vague requirements or undefined terms?

The clarity assessment identifies vague language and undefined terms that block implementation. The review flags these issues explicitly so you can refine definitions, clarify constraints, and resolve ambiguities before handoff to the development team.