spec-update

Specification updates ensure docs reflect implementation by comparing branches, analyzing diffs, and identifying gaps between code and specs. Use branch comparison to detect changes, then generate updated documentation that aligns specs with current entities, commands, queries, and events in your system.

Yes. Automate spec updates by comparing feature branches against main, generating diffs that reveal implementation changes, then applying those findings to verify and update specifications. This verifies alignment and catches gaps before merge.

Verification compares specs against code through diff generation and cross-reference analysis. Run branch analysis to detect what changed, identify gaps between documented and actual behavior, then update specs to reflect current implementation for entities, commands, queries, and events.

Branch comparison generates diffs showing code changes between versions. Analyze those diffs to discover what implementation changed, cross-reference against specifications, identify documentation gaps, then update specs to reflect the current code state.

Yes. The process uses git branch analysis and diff generation to compare versions, detect changes, and validate alignment. Branch comparison against main reveals implementation shifts requiring specification updates.

Misalignment creates gaps between documented and actual behavior. Gap analysis identifies discrepancies through diff comparison and cross-reference validation. Specification updates close those gaps and verify that docs accurately reflect entities, commands, queries, and events in the current codebase.