speckit-converge

Compare code against spec, plan, and tasks to append convergence tasks.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/fhlta/primecore --skill speckit-converge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-converge
Source: https://github.com/fhlta/primecore/tree/main/.agents/skills/speckit-converge
Command: npx skills add https://github.com/fhlta/primecore --skill speckit-converge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the manual, error-prone work of tracking gaps between feature specifications, implementation plans, task lists, and actual code for teams using the spec-kit workflow, ensuring no required work is missed after implementation runs.

Core Features & Use Cases

  • Gap Assessment: Automatically compares current code against spec.md, plan.md, and tasks.md to identify unmet requirements, partial implementations, and conflicting code.
  • Severity Classification: Ranks findings by severity (CRITICAL, HIGH, MEDIUM, LOW) based on impact to functionality and alignment with project constitution rules.
  • Append-Only Task Generation: Adds only new, traceable convergence tasks to the end of tasks.md without modifying existing tasks, specs, plans, or application code.
  • Use Case: After running /speckit-implement on a feature, use this Skill to automatically surface any leftover work needed to fully meet the spec, so teams don't have to manually audit the codebase.

Quick Start

Use the speckit-converge skill to assess your current feature implementation against its spec and append any remaining missing tasks to tasks.md.

Frequently Asked Questions about speckit-converge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check for unmet requirements after running a feature implementation?

To check for unmet requirements after implementation, you can automatically compare your current codebase against spec.md, plan.md, and tasks.md to identify partial implementations and conflicting code through gap analysis.

How does append-only task generation work for spec-kit convergence?

Append-only task generation adds only new, traceable convergence tasks to the end of tasks.md without modifying existing tasks, specs, plans, or application code, preserving your project history while surfacing remaining work.

When do I need to validate feature specifications against my codebase?

You need to validate feature specifications against your codebase during post-implementation workflows to ensure no required work was missed, automatically surfacing leftover tasks needed to fully meet the spec.

Can I use gap analysis to classify codebase issues by severity?

Yes, gap analysis ranks findings by severity levels—CRITICAL, HIGH, MEDIUM, and LOW—based on impact to functionality and alignment with project constitution rules, helping prioritize convergence tasks effectively.

Does convergence task generation modify existing application code or specs?

No, convergence task generation does not modify existing application code, specs, or plans. It only generates traceable, append-only tasks in tasks.md aligned with your project constitution constraints.

What is the best way to align code with specs without manual codebase audits?

The best way to align code with specs without manual audits is to automatically compare your codebase against feature specifications and implementation plans, generating traceable convergence tasks for any identified gaps.