specs-review

To audit spec-driven documentation for drift, you must verify structural completeness across Vision, PRD, Goals, and Architecture files while checking ticket lifecycle statuses. This detects mismatches between the codebase and specs, highlights documentation gaps, and recommends targeted remediation steps.

Spec documentation drift occurs when your codebase implementation diverges from your written Vision, PRD, Goals, and Architecture specifications. You detect this drift by auditing structural completeness, evaluating document quality, analyzing ticket frontmatter, and cross-referencing specs against current code implementation.

Check structural completeness by verifying your project exposes required spec files and folders like specs/README.md, specs/Vision.md, specs/PRD.md, specs/Goals.md, specs/Architecture/README.md, specs/Glossary.md, specs/Changelog.md, specs/decisions/, and specs/tickets/.

Yes, you can use a spec audit to validate ticket health by checking ticket frontmatter, analyzing lifecycle statuses, and ensuring README and decisions reflect the current state. It also validates cross-references between your project architecture specs and related tickets.

You need to run a spec health audit when ensuring specs are up to date, detecting drift between code and documentation, or auditing alignment across Vision, PRD, Goals, and Architecture. It is essential when evaluating changelog freshness and cross-document references.

The best way to evaluate document quality is auditing vision, problem statements, functional and non-functional requirements, scope, glossary usage, and changelog freshness. This ensures your PRD and architecture documents maintain high consistency and accurate cross-references.