speckit-converge

Codebase and feature spec alignment is the process of identifying discrepancies between documented intent and actual implementation. This skill parses project artifacts to find missing requirements and generate actionable tasks, ensuring continuous alignment between design and code.

To check if your codebase matches the project plan, run an automated gap analysis. This skill compares your current codebase against spec.md, plan.md, and tasks.md to identify missing requirements or contradictions, ensuring no criteria are overlooked.

You can generate traceable tasks from missing feature requirements by running an automated gap analysis against your specification files. This skill appends actionable, traceable tasks directly to tasks.md for developers to implement.

Yes, you can use specification files to verify acceptance criteria after a development sprint. Run this skill to assess the current directory and ensure all acceptance criteria from your feature specification are fully satisfied in the code.

The best way to prevent drift between feature specs and code implementation is continuous alignment. This skill handles drift resolution by parsing project artifacts to generate append-only tasks, bridging high-level design intent and low-level code state.

Yes, you need spec.md, plan.md, and tasks.md files to run a gap analysis. The skill operates by parsing these specific project artifacts to identify contradictions and generate actionable implementation tasks for developers.