speckit-converge

To check if your codebase matches feature specifications, you need an automated gap analysis that compares current code against requirements and acceptance criteria. This skill parses project artifacts to pinpoint missing, partial, or contradictory implementations relative to your plans.

Codebase drift occurs when actual code diverges from project documentation. You identify missing requirements by running a deterministic assessment of feature specs and technical plans against the current implementation to detect discrepancies and unresolved work items.

You can automatically generate development tasks from acceptance criteria by assessing requirement gaps and appending actionable work items to a task tracking file. This ensures traceable task generation directly from unfulfilled feature specifications.

No, this gap analysis tool requires no external dependencies. It operates independently using internal scripts to parse project artifacts and append missing work items to your task tracking file.

Yes, you can verify code alignment and constitution principles after a coding session by running a convergence check. It performs a deterministic assessment of requirements to ensure no implementation gaps remain before finalizing the feature.

The best way to track missing work items from technical plans is to automatically append generated tasks to a tasks.md file. This approach ensures all discrepancies between specs and code are captured as actionable development tasks for subsequent implementation.