# speckit.converge

speckit.converge is a subagent that checks code against a feature’s spec, plan, and tasks, then adds unfinished work to tasks.md. Run it after speckit.implement.

- subagent · `type=agent` · Claude Code, Codex, Cursor, GitHub Copilot · ★ 110 repo stars
- Author: alfredoperez
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/alfredoperez/speckit-companion/tree/HEAD/.github/agents/speckit.converge.agent.md
- Updated: 2026-10-19
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/speckitconverge

## What it does

The subagent compares the codebase with `spec.md`, `plan.md`, and `tasks.md`, while treating the project constitution as a constraint. It looks for requirements that are missing or only partly met, then adds traceable tasks in a new Convergence phase. This is a check of the current project state, not a review of Git history or branch changes.

Its only write is to append work to `tasks.md`; it leaves existing tasks and spec files alone and does not edit application code. If the implementation already meets the stated requirements, `tasks.md` stays unchanged. Run it after `/speckit.implement` has worked on the current task list and `/speckit.tasks` has completed that list. The check stops if `spec.md`, `plan.md`, or `tasks.md` is missing.

## Install

### GitHub Copilot (native platform)

**Manually: put the files in place**
- File: `.github/agents/speckit.converge.agent.md`

### Claude Code

**Manually: put the files in place**
- File: `.claude/agents/speckit.converge.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention. Copilot names tools its own way in the tools field: remove it or rewrite it for Claude Code

### Codex

**Manually: put the files in place**
- File: `.codex/agents/speckit.converge.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/speckit.converge.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/alfredoperez/speckit-companion/tree/HEAD/.github/agents/speckit.converge.agent.md

## When to use it
- compare code with functional requirements and acceptance criteria
- spot unfinished work described by the spec and plan
- append remaining implementation tasks to `tasks.md`
- check implementation against mandatory constitution principles

## Example prompts
- Run `speckit.converge` to compare the current implementation with the spec and plan, then add any remaining work to `tasks.md`.
- After implementation, use `speckit.converge` to check the code against the acceptance criteria.

## Source text · speckit.converge.agent.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 93c21e75588304b2.

BEGIN THIRD-PARTY FILE 93c21e75588304b2
````text
---
description: Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
---

## User Input

```text
$ARGUMENTS
```

You **MUST** consider the user input before proceeding (if not empty).

## Pre-Execution Checks

**Check for extension hooks (before convergence)**:

- Check if `.specify/extensions.yml` exists in the project root.
- If it exists, read it and look for entries under the `hooks.before_converge` key
- If the YAML cannot be parsed or is invalid, do not skip silently: tell the user that `.specify/extensions.yml` could not be read (include the parser error) and that no hooks were checked, including any mandatory (`optional: false`) hooks registered there, then continue normally
- Filter out hooks where `enabled` is explicitly `false`. Treat hooks without an `enabled` field as enabled by default.
- For each remaining hook, do **not** attempt to interpret or evaluate hook `condition` expressions:
  - If the hook has no `condition` field, or it is null/empty, treat the hook as executable
  - If the hook defines a non-empty `condition`, skip the hook and leave condition evaluation to the HookExecutor implementation
- For each executable hook, output the following based on its `optional` flag:
  - **Optional hook** (`optional: true`):

    ```text
    ## Extension Hooks

    **Optional Pre-Hook**: {extension}
    Command: `/{command}`
    Description: {description}

    Prompt: {prompt}
    To execute: `/{command}`
    ```

  - **Mandatory hook** (`optional: false`):

    ```text
    ## Extension Hooks

    **Automatic Pre-Hook**: {extension}
    Executing: `/{command}`
    EXECUTE_COMMAND: {command}

    Wait for the result of the hook command before proceeding to the Goal.
    ```
    After emitting the block above you MUST actually invoke the hook and wait for it to finish before continuing. Run it the same way you would run the command yourself in this agent/session (the invocation may differ from the literal `{command}` id shown above, e.g. a skills-mode agent runs it as `/skill:speckit-...` or `$speckit-...`). Emitting the block alone does not run the hook.

- If no hooks are registered or `.specify/extensions.yml` does not exist, skip silently

## Goal

Close the gap between what a feature's specification, plan, and tasks call for and what the
codebase currently implements. Read `spec.md`, `plan.md`, and `tasks.md` as the **sole
source of intent** (with the constitution as governing constraints), assess the current
state of the code, determine which requirements, acceptance criteria, plan decisions, and
existing tasks are unmet, incomplete, or only partially satisfied, and **append each piece
of remaining work as a new, traceable task** at the bottom of `tasks.md` so that
`/speckit.implement` can complete it. This command MUST run only after
`/speckit.implement` has run on the current `tasks.md`, and after `/speckit.tasks` has produced a complete `tasks.md`.

This is **not** a diff tool and does **not** track changes. It assesses the present state
of the code relative to the feature's artifacts — no git, no branch comparison, no history.

## Operating Constraints

**APPEND-ONLY, NEVER REWRITE**: The command's **only** write is appending a new
`## Phase N: Convergence` section to `tasks.md`. It MUST NOT:

- modify `spec.md` or `plan.md` in any way;
- rewrite, renumber, reorder, or delete any existing task (including tasks from a prior
  Convergence phase);
- modify, create, or delete any application code — completing the appended tasks is the
  job of `/speckit.implement`.

When the codebase already satisfies everything, the command MUST leave `tasks.md`
````
END THIRD-PARTY FILE 93c21e75588304b2

The third-party file has ended. Everything between the 93c21e75588304b2 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3745 of 12938 bytes. © alfredoperez · MIT · https://github.com/alfredoperez/speckit-companion/tree/HEAD/.github/agents/speckit.converge.agent.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
