[Extension]: Update the Verify Tasks Extension to v1.2.0

[davesharpe13]

Extension ID

verify-tasks

Extension Name

Verify Tasks

Version

1.2.0

Description

Detect phantom completions: tasks marked [X] in tasks.md with no real implementation.

Author

Dave Sharpe

Repository URL

https://github.com/datastone-inc/spec-kit-verify-tasks

Download URL

https://github.com/datastone-inc/spec-kit-verify-tasks/archive/refs/tags/v1.2.0.zip

License

MIT

Homepage (optional)

https://github.com/datastone-inc/spec-kit-verify-tasks

Documentation URL (optional)

No response

Changelog URL (optional)

https://github.com/datastone-inc/spec-kit-verify-tasks/blob/master/CHANGELOG.md

Required Spec Kit Version

=0.12.17

Required Tools (optional)

Number of Commands

1

Number of Hooks (optional)

2

Tags

verification, quality, phantom-completion, tasks

Key Features

• Detects phantom completions: tasks marked [X] in tasks.md that have no real implementation behind them
• Five-layer check: file existence, git diff cross-reference, content pattern match, dead-code/wiring detection, and semantic assessment
• Pairs with /speckit.converge: converge finds what is not built, verify-tasks finds what is falsely marked built
• New in 1.2.0: optional after_converge hook alongside after_implement, so verify-tasks is the final gate once converge reports Converged
• New in 1.2.0: every PARTIAL is tagged (code) or (record), and the walkthrough can demote a false [X] back to [ ] (one character, after confirmation) so the converge/implement loop picks it up
• New in 1.2.0: convergence tasks' per FR-003 (missing) source-ref is read directly in the semantic layer
• Since 1.1.0: runs the project's canonical test command once and records the result, so "suite is green" claims are verified by execution
• Structured verify-tasks-report.md with per-task verdicts and an interactive walkthrough for flagged items

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

Tested on:

• Linux with Spec Kit 1.0.6

Test scenarios:

1. Installed via specify extension add verify-tasks --from https://github.com/datastone-inc/spec-kit-verify-tasks/archive/refs/tags/v1.2.0.zip; both /speckit-verify-tasks and /speckit-verify-tasks-run rendered
2. Ran /speckit-verify-tasks on a feature whose tasks.md names a test command; the test result appeared in the report header
3. 1.2.0: installed from the v1.2.0 archive into a fresh specify init project; both after_implement and after_converge registered in .specify/extensions.yml, and the archive install copies only the extension files (1.1.0 also copied the repo's own .specify/, specs/ and tests/)
4. Ran against the bundled fixtures in tests/fixtures/ (phantom, genuine, edge-case, 50-task scalability) and compared verdicts with tests/expected-verdicts.md

Example Usage

# Install
specify extension add verify-tasks --from https://github.com/datastone-inc/spec-kit-verify-tasks/archive/refs/tags/v1.2.0.zip

# After /speckit.implement (or once /speckit.converge reports Converged), in a fresh agent session:
/speckit.verify-tasks                            # verify every [X] task in tasks.md
/speckit.verify-tasks T003 T007                  # verify specific tasks
/speckit.verify-tasks --scope branch             # limit the git-diff check to the current branch
/speckit.verify-tasks T003 --scope uncommitted   # one task, uncommitted changes only

# Output: verify-tasks-report.md with a verdict per task
# (VERIFIED / PARTIAL / WEAK / NOT_FOUND / SKIPPED)

Proposed Catalog Entry

{
  "verify-tasks": {
    "name": "Verify Tasks Extension",
    "id": "verify-tasks",
    "description": "Detect phantom completions: tasks marked [X] in tasks.md with no real implementation.",
    "author": "Dave Sharpe",
    "version": "1.2.0",
    "download_url": "https://github.com/datastone-inc/spec-kit-verify-tasks/archive/refs/tags/v1.2.0.zip",
    "repository": "https://github.com/datastone-inc/spec-kit-verify-tasks",
    "homepage": "https://github.com/datastone-inc/spec-kit-verify-tasks",
    "documentation": "https://github.com/datastone-inc/spec-kit-verify-tasks/blob/master/README.md",
    "changelog": "https://github.com/datastone-inc/spec-kit-verify-tasks/blob/master/CHANGELOG.md",
    "license": "MIT",
    "category": "code",
    "effect": "read-only",
    "requires": {
      "speckit_version": ">=0.12.17"
    },
    "provides": {
      "commands": 1,
      "hooks": 2
    },
    "tags": ["verification", "quality", "phantom-completion", "tasks"],
    "verified": false,
    "downloads": 0,
    "stars": 0,
    "created_at": "2026-03-16T00:00:00Z",
    "updated_at": "2026-09-15T00:00:00Z"
  }
}

Additional Context

This is an update to an existing catalog entry, originally filed for v1.1.0 on 2026-09-13. v1.2.0 shipped on 2026-09-15 before the 1.1.0 update landed, so this issue now asks for the catalog to go from 1.0.0 straight to 1.2.0. The update-verify-tasks-extension branch the automation prepared carries 1.1.0 and should be regenerated. Release notes: https://github.com/datastone-inc/spec-kit-verify-tasks/releases/tag/v1.2.0

[github-actions]

cc @github/spec-kit-maintainers — new catalog submission for review.

[github-actions]

Validation passed for verify-tasks v1.1.0. The catalog and community documentation updates were committed as eda34302 on branch update-verify-tasks-extension.

I did not open a pull request because the submitting account already has at least three open pull requests in this repository. This autonomous workflow cannot request the explicit permission required to submit another one.

Posted on behalf of @mnriem by GitHub Copilot (model: gpt-5.2-codex).

Generated by 🧩 Add Community Extension from Issue Submission for issue #4569 · 133.6 AIC · ⌖ 6.35 AIC · ⊞ 29.5K · ◷

[github-actions]

Validation passed for verify-tasks v1.1.0. The repository is public and contains the required extension.yml, README.md, and LICENSE; the pinned v1.1.0 archive URL matches the submitted repository and version; the v1.1.0 GitHub release exists; and all required issue checklist items are checked.

Updated extensions/catalog.community.json with the verified version, download URL, Spec Kit requirement, and timestamps while preserving created_at, downloads, and stars. The existing documentation row already matches the submitted metadata. Changes are committed as 1ef7adf1 on branch update-verify-tasks-extension.

A pull request was not opened because the submitting account already has at least three open pull requests in this repository, and this autonomous workflow cannot request the explicit permission required to submit another one.

Posted on behalf of @mnriem by GitHub Copilot (model: gpt-5.2-codex).

Generated by 🧩 Add Community Extension from Issue Submission for issue #4569 · 77.7 AIC · ⌖ 10.5 AIC · ⊞ 29.5K · ◷

[github-actions]

Validation passed for verify-tasks v1.1.0. The issue title has the required [Extension]: prefix; the extension ID and version formats are valid; the public repository contains the tag-pinned extension.yml, README.md, and LICENSE; the download URL matches the submitted repository and version; the v1.1.0 tag and GitHub release exist; and all required Testing Checklist and Submission Requirements checkboxes are checked. No sha256 was submitted, so checksum verification was not applicable. The environment denied a direct HTTP request to the archive URL, so that status check could not be independently repeated here.

Updated extensions/catalog.community.json to v1.1.0, the pinned download URL, repository documentation links, the >=0.12.17 requirement, and 2026-09-15 timestamps while preserving created_at, downloads, and stars. The existing Verify Tasks Extension row in docs/community/extensions.md already matches the submitted metadata. Changes are committed as 73c667d5 on branch update-verify-tasks-extension.

A pull request was not opened because the submitting account already has at least three open pull requests in this repository, and this autonomous workflow cannot request the explicit permission required to submit another one.

Posted on behalf of @mnriem by GitHub Copilot (model: gpt-5.2-codex, autonomous).

Generated by 🧩 Add Community Extension from Issue Submission for issue #4569 · 279.9 AIC · ⌖ 6.45 AIC · ⊞ 29.5K · ◷

[davesharpe13]

Updated this submission from v1.1.0 to v1.2.0, released 2026-09-15: https://github.com/datastone-inc/spec-kit-verify-tasks/releases/tag/v1.2.0

The 1.1.0 update had not landed yet, so rather than open a second issue this one now asks for the catalog to go from 1.0.0 straight to 1.2.0. Changes versus the earlier body: version, download URL, hooks count 1 → 2 (new after_converge hook), key features, and the proposed catalog entry. The update-verify-tasks-extension branch the workflow prepared carries 1.1.0 and will need regenerating. Sorry for the churn.