speckit-version-guard-check

What problem does it solve?

It prevents plan/task/implement phases from relying on outdated or mismatched locked dependency versions by verifying them against live registries and capturing security and upgrade-relevant evidence in a constraints artifact.

Core Features & Use Cases

• Resolves locked versions from npm/pnpm/yarn lockfiles (with defined precedence across repo root, frontend, and backend), producing an authoritative “locked vs latest” status table.
• Checks known issues by consulting vulnerability sources (e.g., advisories/audit signals) and recording severity and patched-in guidance for flagged packages.
• Generates mandatory compatibility rules derived from migration documentation so downstream steps must follow locked-version-safe APIs.
• Writes a version-guard-report.md artifact into the active feature directory for subsequent Speckit phases to load without re-fetching.

Quick Start

Ask the AI to run speckit-version-guard-check before planning and then use the generated version-guard-report.md constraints to drive all later implementation decisions for the locked dependencies.