skills.rest
WolframResearch
WolframResearchOFFICIAL
Explore all skills by this author →
WebsiteGitHub

review-spec

Cross-reference design specifications against the current codebase to surface inaccuracies and gaps.

82|19|Updated Mar 21, 2025
Search Tags:#design#codebase#qa#verification#audit#review#spec
One-click install
npx skills add https://github.com/WolframResearch/AgentTools --skill review-spec-wolframresearch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-spec
Source: https://github.com/WolframResearch/AgentTools/tree/main/.claude/skills/review-spec
Command: npx skills add https://github.com/WolframResearch/AgentTools --skill review-spec-wolframresearch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review a design specification against the actual codebase to surface inaccuracies, missing details, or issues before implementation, reducing rework and misalignment.

Core Features & Use Cases

  • Cross-check specifications against implementation to verify behavior, interfaces, and constraints align with code.
  • Flag inconsistencies, ambiguities, or missing touchpoints that could derail development.
  • Audit for conventions, guardrails, and coding standards to ensure alignment with project practices.

Quick Start

Provide the path to a spec (e.g., Specs/feature.md) and request a full cross-check against the current codebase.

Frequently Asked Questions about review-spec

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

FAQPage Schema
How do I audit a design specification against my codebase to find inconsistencies?▼

To audit a design specification, cross-reference the spec against the codebase to surface inaccuracies and gaps. This validates behavior, interfaces, and constraints to flag missing touchpoints and reduce development rework.

What is the best way to verify codebase implementation matches design specs before development?▼

Verifying implementation against design specs requires cross-checking referenced files, function signatures, and option defaults. This surfaces ambiguities and ensures alignment with existing project conventions and coding standards.

Can I check a specification for missing touchpoints and coding convention violations?▼

Yes, you can check a specification for missing touchpoints by auditing it against current codebase conventions. This highlights clear issues, validates changes, and ensures guardrails are maintained across the project.

How do I review a feature spec to ensure function signatures and file paths are accurate?▼

Reviewing a feature spec involves reading referenced files and validating function signatures and file paths against the actual codebase. This cross-checking process highlights inaccuracies and missing details before implementation.

Why does my design specification review fail to catch codebase misalignment and ambiguities?▼

A design specification review misses misalignment when it fails to cross-reference option defaults and file paths with the codebase. Applying a thorough audit surfaces these gaps and flags inconsistencies early.

Does reviewing specs against a codebase require providing specific file paths?▼

Yes, reviewing specs requires providing the path to the specification document, such as Specs/feature.md. This allows the audit to read referenced files and validate changes against the current codebase implementation.

Related Skills

Explore More Software Engineering Skills→
rubykachurubykachu
1

agents-md-generator

Generate and update AGENTS.md files with hierarchical coding conventions.

Community
Advanced
foutoucourfoutoucour

test-check

Classify modified functions' test statuses and update or create tests.

Community
Advanced
DarkMonkDevDarkMonkDev
1

test-environment

Run unit, integration, and end-to-end tests in isolated containers.

Community
Advanced
joshsmithxrmjoshsmithxrm
5

spec-audit

Audit specifications against codebases to identify drift, gaps, and undocumented behavior.

Community
Advanced