reassess-spec

To audit a spec file, you can run a reassessment workflow that validates the spec against your codebase and FOUNDATIONS.md. This process identifies compatibility gaps, generates a findings report for approval, and writes the updated spec back to the target file.

Spec governance is the process of ensuring roadmap-gate specs align with repository rules and foundation documents. You need to validate specs when you want to surface compatibility gaps, enforce deterministic validation rules, and maintain traceability across your documentation.

Yes, you can automatically update documentation specs located under specs/, docs/, and .claude/skills/. The workflow presents identified issues and improvements for your decision-making, then applies approved changes by writing the updated spec back to the target file.

You ensure codebase alignment by running a pre-apply verification workflow that enforces deterministic validation rules and FOUNDATIONS conformance. This generates a findings report detailing issues, improvements, and additions before you approve any updates.

The best way to enforce deterministic validation rules is to reassess the specs against the current repository and docs/FOUNDATIONS.md. This identifies misalignments and produces an updated spec file only after user approval, ensuring strict conformance and traceability.

Yes, a docs/FOUNDATIONS.md document is required to perform a spec audit. The reassessment process relies on checking specs against these foundation rules to identify compatibility gaps, enforce conformance, and generate accurate findings for user approval.