One-click install
npx skills add https://github.com/OpenElementsLabs/claude-base --skill spec-review-openelementslabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-review
Source: https://github.com/OpenElementsLabs/claude-base/tree/main/claude-project-base/skills/spec-review
Command: npx skills add https://github.com/OpenElementsLabs/claude-base --skill spec-review-openelementslabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identifies and verifies that a code implementation fully satisfies its associated spec by cross-checking design and behavioral documentation against the code and tests.

Core Features & Use Cases

  • Design coverage assessment: Verifies mapping between spec.design.md and code/data models.
  • Behavior coverage validation: Evaluates spec.behaviors.md against implemented tests and code paths.
  • Audit trail generation: Produces a structured report detailing gaps, confidence, and recommended actions for remediation.

Quick Start

Provide the spec name or target feature to review, and run the skill to generate a design and behavior coverage report.

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 its design and behavioral specs?

You can verify code against specs by cross-checking design.md and behaviors.md documentation against the codebase and tests to identify gaps, flag drift, and produce a structured remediation report.

What does design coverage assessment check in a codebase?

Design coverage assessment verifies the mapping between spec.design.md and the actual code or data models, ensuring the implementation fully satisfies the documented architectural design.

How can I validate behavior coverage from my testing suite?

Behavior coverage validation evaluates spec.behaviors.md against implemented tests and code paths, confirming that all documented functional requirements are exercised by the suite.

Does spec-review work without external dependencies?

Yes, spec-review operates with zero external dependencies, requiring only the target spec directory containing design.md and behaviors.md files alongside the codebase and tests for analysis.

What is the best way to audit traceability between specs and tests?

The best way to audit traceability is to read the behavioral and design documentation fully, compare it to implemented code paths, and generate an audit trail detailing confidence and recommended actions.

Can I generate a structured report for spec drift and coverage gaps?

Yes, you can generate a structured report detailing design coverage, behavior coverage, confidence levels, and recommended actions to remediate any identified gaps or spec drift.