Extension ID

reconcile

Extension Name

Reconcile Extension

Version

1.3.1

Description

Reconcile implementation drift by surgically updating the feature's own spec, plan, and tasks.

Author

Stanislav Deviatov

Repository URL

https://github.com/stn1slv/spec-kit-reconcile

Download URL

https://github.com/stn1slv/spec-kit-reconcile/archive/refs/tags/v1.3.1.zip

License

MIT

Homepage (optional)

https://github.com/stn1slv/spec-kit-reconcile

Documentation URL (optional)

https://github.com/stn1slv/spec-kit-reconcile/blob/main/README.md

Changelog URL (optional)

https://github.com/stn1slv/spec-kit-reconcile/blob/main/CHANGELOG.md

Required Spec Kit Version

=0.16.2

Required Tools (optional)

No response

Number of Commands

1

Number of Hooks (optional)

2

Tags

reconcile, drift, tasks, remediation

Key Features

This updates the existing reconcile entry from v1.2.1 to v1.3.1. Besides the version, the download URL and updated_at, the proposed entry adds the optional sha256; the requirements, command count, hook count and tags stay the same.

Reconcile is opt-in extension reconciliation that can run during or after delivery, as the docs merged in #4945 and #4948 describe. It records discoveries the team has accepted; the implementation is evidence for that decision, not the source of intent:

• Every run asks, before any edit, which drift items the team approves reconciling into the artifacts. Items left out are written nowhere, and the report recommends /speckit.converge for them. "Approve none" writes nothing.
• When the constitution says the project uses flow-forward, the run writes nothing, asks nothing, and recommends a new feature directory with /speckit.specify.
• Revision notes carry an Approved: line naming the approved items, so the decision stays next to the edits it allowed.
• An open converge task written against an entry the run amends is named first in the Next Step, so the team resolves it before /speckit.implement; the task itself is never edited.
• The Next Step routes new work back through /speckit.implement and /speckit.converge.

Optional sha256 of the release archive: 651537ba453f519b33c61ceb0c63d30bea04bd7fd81b83a4f7bdde86eb39adb5

Testing Checklist

• Extension installs successfully via download URL
• All commands execute without errors
• Documentation is complete and accurate
• No security vulnerabilities identified
• Tested on at least one real project

Submission Requirements

• Valid extension.yml manifest included
• README.md with installation and usage instructions
• LICENSE file included
• GitHub release created with version tag
• All command files exist and are properly formatted
• Extension ID follows naming conventions (lowercase-with-hyphens)

Testing Details

Installed v1.3.1 from the download URL above into a fresh specify init project (Claude Code integration, sh scripts) on macOS. The install succeeded, the rendered skill carries no unresolved __SPECKIT_COMMAND_* tokens and no unrewritten relative script paths, the /speckit.specify and /speckit.converge references render in the agent's own form, both hooks register on after_implement and after_converge, and the installed tree contains only the extension.

Behaviour testing is fixture-based. The extension is a prompt, so it is tested by executing it against a fixture project of deliberate traps, with expectations committed before each round that grades them. For v1.3.1, eight cases ran against the release candidate (five existing cases re-run, plus new flow-forward, living-spec and open-converge-task cases). A review of the branch by five models led to fixes, after which the affected cases re-ran and two new re-run cases were added; all passed. Which cases ran against which commit, and the gaps still open, are in tests/fixture/BASELINE-v1.3.1.md. The previous version, v1.3.0, was also run by the author on a private project; v1.3.1 has been verified on the fixture and the fresh install above.

The extension executes no code of its own. It reads artifacts and calls the check-prerequisites.sh and resolve-template.sh scripts that Spec Kit already ships.

Example Usage

/speckit.reconcile.run specs/007-invoice-settings Backend exists, but the React screen is unreachable; need sidebar link and route

Proposed Catalog Entry

{
  "name": "Reconcile Extension",
  "id": "reconcile",
  "description": "Reconcile implementation drift by surgically updating the feature's own spec, plan, and tasks.",
  "author": "Stanislav Deviatov",
  "version": "1.3.1",
  "download_url": "https://github.com/stn1slv/spec-kit-reconcile/archive/refs/tags/v1.3.1.zip",
  "repository": "https://github.com/stn1slv/spec-kit-reconcile",
  "homepage": "https://github.com/stn1slv/spec-kit-reconcile",
  "documentation": "https://github.com/stn1slv/spec-kit-reconcile/blob/main/README.md",
  "changelog": "https://github.com/stn1slv/spec-kit-reconcile/blob/main/CHANGELOG.md",
  "license": "MIT",
  "category": "docs",
  "effect": "read-write",
  "sha256": "651537ba453f519b33c61ceb0c63d30bea04bd7fd81b83a4f7bdde86eb39adb5",
  "requires": {
    "speckit_version": ">=0.16.2"
  },
  "provides": {
    "commands": 1,
    "hooks": 2
  },
  "tags": [
    "reconcile",
    "drift",
    "tasks",
    "remediation"
  ],
  "verified": false,
  "downloads": 0,
  "stars": 0,
  "created_at": "2026-03-14T00:00:00Z",
  "updated_at": "2026-10-13T00:00:00Z"
}

Additional Context

This is an update to an existing catalog entry rather than a new extension, filed as a fresh submission issue per the Extension Publishing Guide.