skills.rest
nesquikm
nesquikmCOMMUNITY
Explore all skills by this author →
GitHub

spec-review

Audit code implementations against formal specifications to reveal deviations and gaps.

6|Updated Mar 19, 2026
Search Tags:#specifications#traceability#drift-detection#acceptance-criteria#code-audit#spec-review
One-click install
npx skills add https://github.com/nesquikm/dev-process-toolkit --skill spec-review-nesquikm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-review
Source: https://github.com/nesquikm/dev-process-toolkit/tree/main/plugins/dev-process-toolkit/skills/spec-review
Command: npx skills add https://github.com/nesquikm/dev-process-toolkit --skill spec-review-nesquikm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Review teams need a reliable way to verify that code implements defined specifications, surfacing deviations and gaps to reduce drift and rework.

Core Features & Use Cases

  • Spec-to-code alignment checks across FRs and ACs
  • Automated traceability mapping from requirements to implementations and tests
  • Drift detection between specs and code in tracker-mode or local specs
  • Comprehensive audit reports highlighting gaps, inconsistencies, and potential improvements

Quick Start

Run the spec-review with a specific requirement ID or 'all' to generate a traceability audit.

Frequently Asked Questions about spec-review

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

FAQPage Schema
How do I audit code against specifications to find deviations?▼

Spec drift detection compares current code implementations against formal FRs and ACs to identify deviations. It scans implementations and generates a traceability report mapping coverage gaps and inconsistencies per acceptance criteria.

What is traceability mapping for acceptance criteria?▼

Traceability mapping for acceptance criteria links formal requirements directly to code implementations and tests. It generates a report detailing implementation and test coverage per AC to expose alignment gaps.

How do I detect spec drift between requirements and code?▼

Detect spec drift by scanning code implementations against local specs or tracker-mode requirements. This reveals gaps where the codebase deviates from defined formal specifications and acceptance criteria.

Does spec review work with local specs and tracker mode?▼

Yes, spec review supports both local specs and tracker mode. It requires accessing formal requirements in specs/frs and specs/plan directories, scanning implementations, and generating a traceability audit report.

What is the best way to check per-acceptance-criteria implementation coverage?▼

The best way to check per-acceptance-criteria implementation coverage is running an audit across all FRs and ACs. This generates a traceability report detailing implementation and test coverage gaps per requirement ID.

When should I not use automated spec-to-code alignment checks?▼

Avoid automated spec-to-code alignment checks if your project lacks defined formal requirements and acceptance criteria. The audit requires structured specs in specs/frs and specs/plan to map traceability and detect drift.

Related Skills

Explore More Software Engineering Skills→
Ocean326Ocean326

product-manager

Create PRDs, FRs, NFRs, epics, and user stories from a project brief.

Community
Advanced
specd-sddspecd-sdd
12

specs-compliance

Audit specs against code implementations to detect drift and verify test coverage.

Official
Advanced
hlhr202hlhr202
51

conductor-review

Automate code reviews against project guidelines, design specs, and test suites.

Community
Advanced
AsiaOstrichAsiaOstrich
6

ac-coverage

Map acceptance criteria to tests and generate a traceability matrix.

Community
Advanced