speckit-version-guard-load

Loads version guard constraints from .specify/feature.json and fallback full checks.

2|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-version-guard-load-numu-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-version-guard-load
Source: https://github.com/NUMU-IO/NUMU-api/tree/main/.agents/skills/speckit-version-guard-load
Command: npx skills add https://github.com/NUMU-IO/NUMU-api --skill speckit-version-guard-load-numu-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps task generation and implementation aligned with the latest version guard constraints so downstream work stays compatible with the project’s locked dependency rules.

Core Features & Use Cases

  • Constraint Loading: Reads the current feature’s version guard report and brings compatibility guidance into context before work begins.
  • Fallback Handling: Detects when the report is missing or skipped and re-runs the full version check instead of stopping the workflow.
  • Use Case: A developer is about to generate tasks for a spec-kit feature and needs the agent to respect dependency constraints, current-version references, and CVE warnings before producing code.

Quick Start

Use the speckit-version-guard-load skill to load the current feature’s version guard constraints before generating tasks or implementation.

Frequently Asked Questions about speckit-version-guard-load

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

FAQPage Schema
How do I load version constraints before generating tasks in a spec-kit workflow?

A version guard loader reads .specify/feature.json and version-guard-report.md to inject dependency constraints, current-version references, and CVE warnings into agent context before task generation or implementation begins.

What happens if version-guard-report.md is missing during a spec-kit compatibility check?

When version-guard-report.md is missing, the version guard loader applies graceful degradation by falling back to a full version check, ensuring the workflow continues without stopping due to missing artifacts.

Why should dependency compatibility be checked before spec-kit code implementation?

Checking dependency compatibility before implementation ensures generated code respects locked dependency rules and current-version constraints, preventing downstream integration failures and CVE vulnerabilities.

Does speckit-version-guard-load require any external dependencies to run?

No, it operates with zero external dependencies, relying solely on reading existing spec-kit artifacts like .specify/feature.json and version-guard-report.md to apply compatibility guidance.

When do I need version guard constraints for feature task generation?

You need version guard constraints when your spec-kit feature workflow requires generating tasks or implementing code that must remain compatible with the project's locked dependency rules and security advisories.