speckit.converge

Compare code against spec, plan, and tasks, then append missing work to tasks.md.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/antigravityos187-sketch/universal-or-strategy --skill speckit-converge-antigravityos187-sketch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit.converge
Source: https://github.com/antigravityos187-sketch/universal-or-strategy/tree/main/.bob/skills/speckit.converge
Command: npx skills add https://github.com/antigravityos187-sketch/universal-or-strategy --skill speckit-converge-antigravityos187-sketch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that the current codebase aligns with the feature's specification, plan, and tasks, by assessing and appending any remaining unbuilt work as new tasks.

Core Features & Use Cases

  • Codebase Assessment: Assess the current codebase against the feature's spec, plan, and tasks.
  • Appending Tasks: Append any remaining unbuilt work as new tasks to tasks.md.
  • Use Case: After running /speckit.implement, use /speckit.converge to ensure that the codebase meets all the requirements before proceeding.

Quick Start

Run /speckit.converge to assess the codebase and append any remaining tasks.

Frequently Asked Questions about speckit.converge

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

FAQPage Schema
How do I ensure my codebase aligns with feature specifications and plans?

To ensure codebase alignment with feature specifications, you can assess your current code against your documentation and append any missing features or unbuilt work as new tasks in your task management file.

What is the best way to append missing tasks after implementing a new feature?

The best way to append missing tasks is to compare your current codebase against your feature specification, plan, and task lists to identify gaps, then automatically append remaining unbuilt work as actionable items.

Do I need specific markdown files to perform a codebase review against project plans?

Yes, performing a codebase review against project plans requires access to specific markdown files: spec.md, plan.md, tasks.md, and constitution.md, utilizing YAML and Markdown processing to evaluate specification alignment.

How does specification alignment work when assessing unbuilt feature work?

Specification alignment works by comparing current code against feature specifications and plans, identifying discrepancies, and appending the remaining unbuilt work as new tasks to ensure complete feature coverage before proceeding.

Can I use this code assessment tool after running feature implementation commands?

Yes, you can use this code assessment tool immediately after running feature implementation commands to verify that the codebase meets all requirements and to append any remaining unbuilt work as new tasks.

Why does my codebase still have unbuilt features after completing the planned tasks?

Your codebase might have unbuilt features because the implementation did not fully meet the feature specification, requiring a convergence assessment to identify gaps and append the remaining work as new tasks.