skills.rest
dogganidhal
dogganidhalCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

validate-spec

Compare formal specs against source implementations and generate structured validation reports.

43|1|Updated Feb 19, 2024
Search Tags:#documentation#verification#spec#behavior#validate#invariants#exports
One-click install
npx skills add https://github.com/dogganidhal/noddde --skill validate-spec-dogganidhal
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: validate-spec
Source: https://github.com/dogganidhal/noddde/tree/main/.claude/skills/validate-spec
Command: npx skills add https://github.com/dogganidhal/noddde --skill validate-spec-dogganidhal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validating a software spec against its implementation to prevent drift and ensure alignment between intended design and delivered code.

Core Features & Use Cases

  • Compare spec exports with actual source exports and surface invariants to detect gaps.
  • Audit behavioral requirements, edge cases, and documentation staleness to ensure comprehensive coverage.
  • Generate a structured validation report that highlights gaps, risks, and recommended fixes.

Quick Start

Validate a codebase against its spec by running the dedicated validator to surface export shortfalls and behavioral divergences.

Frequently Asked Questions about validate-spec

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

FAQPage Schema
How do I validate my software spec against implementation to prevent drift?▼

Spec validation compares your formal spec with actual source code to identify and report divergences across exports, behaviors, invariants, and edge cases, ensuring alignment between intended design and delivered code.

What is the best way to check for missing exports and behavioral gaps in my codebase?▼

Run a dedicated validator to compare spec exports with actual source exports, auditing behavioral requirements and edge cases to surface coverage shortfalls and generate a structured validation report.

How does spec validation detect documentation staleness and untested invariants?▼

Spec validation enforces checks for invariants, edge cases, stubs, and documentation consistency across source, test, and spec files, highlighting gaps, risks, and recommended fixes in a structured report.

Can I validate edge cases and stub coverage across source, test, and spec files?▼

Yes, validation audits edge cases, stubs, and behavioral requirements across source, test, and spec files to ensure comprehensive coverage and detect divergences between the formal spec and its implementation.

What limitations should I expect when validating a formal spec against implementation?▼

Validation primarily targets Step 5 of a 6-step pipeline and focuses on exports, behaviors, invariants, edge cases, and documentation consistency, meaning it does not generate fixes automatically but recommends them in the report.

Related Skills

Explore More Software Engineering Skills→
BellaBeBellaBe
37

spec-constraints

Extract invariants, preconditions, postconditions, and laws into constraints.yaml with proof obligations.

Community
Advanced
OpenElementsLabsOpenElementsLabs

spec-review

Cross-check design and behavior specs against code and tests.

Official
Intermediate
yoshisadayoshisada

kiln-init

Initialize kiln in an existing repository with harness, scaffolding, and workflow hooks.

Community
Intermediate
juxtjuxt
10

weed

Resolve divergences between Allium behavioral specification files and implementation code.

Official
Advanced