speckit-converge

To check codebase alignment with project specifications, assess the current code against feature specs, plans, and task lists to identify implementation gaps. Verifying functional requirements and acceptance criteria ensures the code matches project intent.

Tracking missing implementation tasks involves appending identified gaps as traceable tasks to tasks.md. This ensures incomplete work from feature specifications is automatically documented and tracked for future implementation.

Automating gap analysis between spec.md and your current code requires comparing the codebase against defined requirements and architectural decisions. This process automatically detects missing functional requirements and acceptance criteria.

Codebase convergence operates within a spec-kit project structure to verify functional requirements and acceptance criteria. It requires the directory to contain the standard specification, plan, and task tracking files.

Implementation drift from architectural decisions in plan.md occurs when development workflow loses alignment with specifications. Running a convergence assessment identifies these gaps and appends missing work as actionable tasks.

A specification compliance check is needed after implementing a new feature to ensure all acceptance criteria and architectural constraints have been met. It generates a checklist for any remaining items requiring completion.