speckit-converge

Codebase convergence automates alignment between your code and feature specs by assessing the project plan, identifying gaps, and appending missing tasks to `tasks.md`. It requires a spec-kit project structure with a `.specify/` directory.

You generate missing tasks by running an automated codebase assessment against your feature spec and plan. The process identifies gaps and appends incomplete items directly to `tasks.md` for resolution.

Yes, codebase assessment requires a spec-kit project structure containing a `.specify/` directory. This structure provides the specifications and plans needed to evaluate alignment and generate tasks.

Automated codebase convergence is the best way to verify code matches specifications. It compares the codebase against the feature spec and plan, identifying missing features and appending them as actionable tasks.

The `.specify/` directory is required because it stores the spec-kit project structure containing feature specs and plans. The Skill reads this directory to assess codebase alignment and generate missing tasks.

Yes, the convergence process uses Python to automate alignment between the codebase and feature specifications. It applies to software engineering workflows requiring synchronization between code, specs, and project plans.