What problem does it solve? Maintainers of the auto-bmad repo need to know whether new releases of the two npm packages it delegates into — bmad-method and bmad-method-test-architecture-enterprise (TEA) — break the contracts auto-bmad parses, the review-layer asset it ships, or the skills it delegates to, without manually re-reviewing already-checked versions. ## Core Features & Use Cases - Incremental per-package diffing: Downloads published npm tarballs and diffs only what is new since the last-checked stable and prerelease versions, anchored from the README compat blockquote. - Contract-aware classification: Tags every changed file as critical, high, low, shim, or info based on whether it owns a contract auto-bmad parses (sprint-status.yaml grammar, HALT protocol, review_layers schema) or is a delegated bmad-testarch-* skill. - Release-note cross-check and marker updates: Guides cross-referencing GitHub release notes and post-stable commits via gitHead, then offers to advance the README badge, compat blockquote, and CHANGELOG markers. - Use Case: After BMAD ships v6.12.0, run the check to see only the delta since your last verified version, confirm no parsed contract moved, and advance the compatibility markers in one pass. ## Quick Start Run /auto-bmad-compat-check from the root of the auto-bmad repo to check both BMAD packages for compatible new releases.