speckit-converge

Compare project artifacts with the codebase to generate tasks for missing features.

Updated May 9, 2026
One-click install
npx skills add https://github.com/Arthur-Valentim/TODO---LIST --skill speckit-converge-arthur-valentim
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-converge
Source: https://github.com/Arthur-Valentim/TODO---LIST/tree/main/.claude/skills/speckit-converge
Command: npx skills add https://github.com/Arthur-Valentim/TODO---LIST --skill speckit-converge-arthur-valentim

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires extensions.yml, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of identifying gaps between feature specifications, plans, and the current codebase, automatically creating tasks for any remaining work.

Core Features & Use Cases

  • Automated Gap Analysis: Identifies unimplemented or incomplete requirements relative to specifications and tasks.
  • Task Creation: Appends new tasks for remaining work to 'tasks.md'.
  • Pre-Execution Checks: Validates the presence of required project structure and configuration files.
  • Post-Execution Hooks: Supports optional and mandatory extension hooks for further actions.

Quick Start

Run the command to assess your feature's gap and generate tasks for remaining work: /speckit-converge

Frequently Asked Questions about speckit-converge

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

FAQPage Schema
How do I automate feature gap analysis between my project specifications and codebase?

Automated feature gap analysis compares your project artifacts and specifications against the current codebase, identifying unimplemented or incomplete requirements to generate actionable tasks for remaining work.

What is the best way to generate tasks for missing requirements in spec-driven development?

Generating tasks for missing requirements involves comparing specifications with your codebase to detect gaps, then automatically appending new tasks for any remaining work directly to your tasks.md file.

How does spec-driven development gap analysis validate project structure before execution?

Spec-driven gap analysis performs pre-execution checks to validate the presence of required project structure, ensuring the .specify/ directory and configuration files exist before comparing artifacts with the codebase.

Can I use extension hooks for post-execution actions after generating tasks?

Yes, you can use extension hooks for post-execution actions after task generation. The system supports optional and mandatory hooks configured within the .specify/extensions.yml file.

Do I need a .specify directory to run feature gap analysis?

Yes, you need a .specify directory to run feature gap analysis. The process operates within a spec-kit project structure and requires the .specify/extensions.yml file to configure optional hooks.

Why is my spec-kit gap analysis not identifying incomplete requirements correctly?

Gap analysis fails to identify incomplete requirements when the required project structure is missing. Pre-execution checks must validate the .specify/ directory and configuration files before comparing artifacts with the codebase.