speckit-converge

To verify your codebase against feature specifications, you can run a convergence check that assesses current implementation state against spec.md, plan.md, and tasks.md artifacts to identify missing or partial work.

Codebase convergence involves comparing actual implementation against defined requirements and architectural constraints to detect missing, partial, or contradictory implementations, then generating actionable tasks to close those gaps.

You can generate traceable tasks for missing requirements by assessing the codebase against feature specifications and appending new, actionable items directly to your project's tasks.md task ledger.

To enforce architectural principles during implementation, validate code against project-wide non-negotiable constitution principles to ensure full convergence with the intended design and maintain architectural integrity.

Yes, you can use convergence checks for projects with existing task lists. The process assesses the current directory and appends newly identified missing implementation tasks directly to your existing tasks.md file.

When contradictory implementations are found relative to defined requirements, the convergence assessment identifies these conflicts and appends actionable, traceable tasks to the project ledger to resolve them.