speckit-blueprint-validate

You can validate scaffold files by running the validate-scaffold.sh script from the repository root, passing the feature directory path or letting it resolve from the current git branch prefix under specs/.

Scaffold validation checks for blueprint.md presence, verifies all referenced scaffold files exist on disk, and ensures scaffold-mode TODO markers remain intact while detecting suspiciously complete implementations that look over-implemented.

You do not strictly need a git branch if you pass the feature directory as an argument. The script resolves FEATURE_DIR from the argument or automatically from the current git branch directory prefix under specs/.

Scaffold validation detects over-implemented files because scaffold mode expects placeholder business logic marked by TODOs. Suspiciously complete implementations indicate the generated scaffold may have deviated from the intended blueprint structure.

No, you cannot check repository consistency without a blueprint. Blueprint presence validation is the first step; the script confirms blueprint.md exists before checking that generated output and referenced files align with it.