speckit-version-guard-load

To load version guard constraints, read the current version-guard report from your Spec Kit repository to make compatibility rules available to the agent context before task generation. This reduces version drift and incompatibility risk during implementation.

If the version guard report is missing or unavailable, fallback handling automatically re-runs the full version check. This ensures constraint loading still surfaces necessary compatibility guidance for subsequent implementation work.

You need to load version constraints before task generation and implementation steps in Spec Kit projects. Loading these rules beforehand ensures generated tasks stay aligned with project compatibility constraints and feature-scoped version guard reports.

Yes, Spec Kit version guard supports handling skip and fallback states when reading version guard artifacts. If constraints are unavailable, it triggers a fallback to re-run the full version check and surface compatibility guidance.

The best way to prevent version drift is loading version guard constraints into agent context before implementation. By reading feature-scoped version guard reports and applying hook-driven workflow steps, you ensure compatibility rules guide task generation.

Version guard loading applies specifically to Spec Kit repositories using feature-scoped version guard reports and hook-driven workflow steps. Without these hooks, the agent may not automatically trigger constraint loading before task generation and implementation.