speckit-sync-analyze

Spec-to-code drift analysis compares specification requirements against implementation artifacts to identify aligned features, unimplemented items, and unspecced code. It maps functional requirements and acceptance scenarios to corresponding commands, services, models, and tests heuristically.

Specification drift analysis identifies where functional requirements and acceptance scenarios diverge from what the codebase implements. You need it when gaps and inconsistencies between specs and code risk going unnoticed during development.

You compare spec-kit requirements by validating the spec directory structure and mapping requirements from spec files to commands, services, entities, and tests. This generates deterministic drift outputs showing aligned, drifted, and unimplemented items.

Yes, analyzing specification drift produces structured reports in both Markdown and JSON formats. These reports detail aligned requirements, drifted behavior, and unimplemented functional or success criteria items for automated processing.

Finding unspecced code involves comparing your implementation against specification files to detect features lacking spec coverage. These features are flagged as candidates for documentation or re-specification.

Drift analysis reports are saved in both human-readable Markdown and machine-readable JSON formats. The generated reports are stored under the .specify/sync directory for review and automation integration.