speckit-converge

To check if your codebase matches feature specifications, you can run an automated gap analysis that compares existing code against spec.md, plan.md, and tasks.md to identify missing or contradictory implementation work.

Automating traceable task generation involves analyzing project artifacts to identify implementation gaps and automatically appending new, actionable tasks to your tasks.md file to resolve those specific discrepancies.

Enforcing constitution principles during code analysis requires validating the codebase against project-specific memory and technical requirements defined in the .specify directory to ensure full compliance.

The best way to align a codebase with feature specs without manual tracking is to use automated convergence tools that assess the current project state and append necessary implementation tasks directly to your task list.

Yes, performing this specific automated gap analysis requires a .specify directory because it contains the constitution principles and technical requirements used to validate codebase compliance and identify implementation gaps.

A codebase convergence check appends tasks instead of modifying source code directly to maintain human control over implementation, ensuring developers manually resolve identified gaps using the newly generated traceable tasks.