How do I install the Validating Specs skill?

Run npx skillmds@latest add tomevault-io/validating-specs in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Validating Specs skill do?

Validates spec claims match codebase reality during /epic-finalize. It is listed under Coding & Dev Tools on SkillMD.

Is Validating Specs safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Validating Specs?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Validating Specs free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Validating Specs?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Validating Specs by tomevault-io — Agent Skill

Name: Validating Specs
Author: tomevault-io

File contents

Workflow

Extract Claims - Parse file paths, symbols, imports, library claims from specs
Verify Files - Glob/Read to confirm paths and line ranges
Verify Symbols - Semantic search + Grep for functions/classes
Verify Libraries - Context7/Exa for third-party feature claims
Check Patterns - Compare proposed implementation against referenced patterns

Severity Levels

Level	Meaning	Behavior
P0	Critical	Blocks (exit 1)
P1	High	Warn (exit 0)
P2	Medium	Advisory

Example Finding

{
  "severity": "P0",
  "category": "file_missing",
  "claim": "Modify hooks/lib/auth_handler.py:45-67",
  "evidence": "File does not exist",
  "suggestion": "Found similar: hooks/lib/authentication.py"
}

Output

═══════════════════════════════════════════════════════════════
   {✓|✗} SPEC VALIDATION: {project} (P0:{n} P1:{n} P2:{n})
═══════════════════════════════════════════════════════════════

Status: {BLOCKED if P0 > 0 else PASSED}

Next:
  BLOCKED → Fix P0 findings, re-validate
  PASSED  → Proceed with /epic-decompose {project}
═══════════════════════════════════════════════════════════════

References

references/validation-steps.md - Detailed workflow
references/output-format.md - JSON structure
references/tool-requirements.md - Tool selection, error handling

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: validating-specsdescription: Validates spec claims match codebase reality during /epic-finalize.---<role>WHO: Spec reality checkerATTITUDE: Specs that reference non-existent files are fiction.</role><purpose>Your job is to verify spec claims against codebase reality. File paths must exist. Symbols must be real. Library assumptions must be accurate. Fiction doesn't ship.</purpose>## Workflow1. **Extract Claims** - Parse file paths, symbols, imports, library claims from specs2. **Verify Files** - Glob/Read to confirm paths and line ranges3. **Verify Symbols** - Semantic search + Grep for functions/classes4. **Verify Libraries** - Context7/Exa for third-party feature claims5. **Check Patterns** - Compare proposed implementation against referenced patterns## Severity Levels| Level | Meaning | Behavior ||-------|---------|----------|| **P0** | Critical | Blocks (exit 1) || **P1** | High | Warn (exit 0) || **P2** | Medium | Advisory |## Example Finding```json{ "severity": "P0", "category": "file_missing", "claim": "Modify hooks/lib/auth_handler.py:45-67", "evidence": "File does not exist", "suggestion": "Found similar: hooks/lib/authentication.py"}```## Output```═══════════════════════════════════════════════════════════════ {✓|✗} SPEC VALIDATION: {project} (P0:{n} P1:{n} P2:{n})═══════════════════════════════════════════════════════════════Status: {BLOCKED if P0 > 0 else PASSED}Next: BLOCKED → Fix P0 findings, re-validate PASSED → Proceed with /epic-decompose {project}═══════════════════════════════════════════════════════════════```## References- `references/validation-steps.md` - Detailed workflow- `references/output-format.md` - JSON structure- `references/tool-requirements.md` - Tool selection, error handling<rules>- P0 blocks - no exceptions- Every claim gets verified - assumptions are bugs- Suggest alternatives for missing files - help fix, not just flag- Use semantic search for symbols - exact match isn't enough</rules>---> Converted and distributed by [TomeVault](https://tomevault.io/claim/davidabeyer) — claim your Tome and manage your conversions.

Frequently asked questions

Validating Specs