vibespec-check

Compare project specifications against source code and report categorized discrepancies.

15|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/v0lka/skills --skill vibespec-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibespec-check
Source: https://github.com/v0lka/skills/tree/main/development/sdd/vibespec-check
Command: npx skills add https://github.com/v0lka/skills --skill vibespec-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discrepancy detection between project specifications and actual code, enabling teams to verify consistency and catch drift after refactors. Use during onboarding or on explicit user request; for every discrepancy found, prompts the user to decide to trust the code, trust the spec, trust neither, or ignore.

Core Features & Use Cases

  • Scope-driven discrepancy analysis across single specs, entire domains, contracts, or full repository scopes.
  • Load and compare specs vs source code at the level of key files, core types, invariants, behavior, configuration, and cross-references.
  • Classify findings into categories such as PATH_MISSING, TYPE_MISMATCH, INTERFACE_DRIFT, BEHAVIOR_DRIFT, CONFIG_DRIFT, INVARIANT_VIOLATED, CROSS_REF_BROKEN, UNDOCUMENTED, and STALE_CONTENT.
  • Interactive decision workflow and guidance on applying fixes, including optional triggers for automated tooling.
  • Generate a concise summary report of discrepancies and resolutions.

Quick Start

Run vibespec-check on a target project to compare specs with code and resolve discrepancies interactively.

Frequently Asked Questions about vibespec-check

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

FAQPage Schema
How do I detect spec-code drift after refactoring a repository?

Detect spec-code drift by loading target specifications and source files to compare claims about key files, types, invariants, behavior, and configuration, reporting categorized discrepancies with recommended resolutions.

What is specification drift and when should I check for discrepancies?

Specification drift occurs when implemented code diverges from project specifications. Check for discrepancies during onboarding, refactors, or maintenance to verify consistency and catch drift across single spec files, entire domains, contracts, or full repository scopes.

How do I resolve mismatches between project specifications and implemented code?

Resolve mismatches interactively by reviewing each discrepancy and deciding whether to trust the code, trust the spec, trust neither, or ignore, then generating a concise summary report of discrepancies and resolutions.

Can I check interface and behavior drift across an entire domain or just single spec files?

You can check interface and behavior drift across single spec files, entire domains, contracts, and full repository scopes. The analysis classifies findings into categories such as INTERFACE_DRIFT, BEHAVIOR_DRIFT, and CONFIG_DRIFT.

What types of discrepancies between specs and source code can be identified?

Discrepancies identified include PATH_MISSING, TYPE_MISMATCH, INTERFACE_DRIFT, BEHAVIOR_DRIFT, CONFIG_DRIFT, INVARIANT_VIOLATED, CROSS_REF_BROKEN, UNDOCUMENTED, and STALE_CONTENT, each accompanied by recommended resolutions.

Does spec-code drift detection work for cross-references and invariants in configuration?

Yes, spec-code drift detection loads and compares specs against source code at the level of cross-references, invariants, and configuration, reporting CROSS_REF_BROKEN, INVARIANT_VIOLATED, and CONFIG_DRIFT discrepancies with interactive decision workflow guidance.