[Extension]: Add specassay-check

[rdryfoos]

Extension ID

specassay-check

Extension Name

SpecAssay Check

Version

0.3.4

Description

Gate 2 refuses silent gaps and emits a trace-manifest (trace-manifest.json).

Author

Rik Dryfoos

Repository URL

https://github.com/rdryfoos/specassay

Download URL

https://github.com/rdryfoos/specassay/releases/download/v0.3.4/specassay-check-0.3.4.zip

License

MIT

Homepage (optional)

https://www.specassay.com

Documentation URL (optional)

https://github.com/rdryfoos/specassay/blob/main/extensions/specassay-check/README.md

Changelog URL (optional)

https://github.com/rdryfoos/specassay/blob/main/CHANGELOG.md

Required Spec Kit Version

=0.14.0

Required Tools (optional)

- bash - required
- python3 (>=3.8) - required

Number of Commands

1

Number of Hooks (optional)

1

Tags

traceability, gate, ci, governance, sdd

Key Features

• Refuses silent acceptance-criterion gaps, invented IDs, and registry/specs/tasks drift
• Emits trace-manifest.json on every run — including refusals — so the evidence trail survives failure
• Honest debt (tracked-debt) and planned work (backlog) pass and stay visible
• Thread Report: one CI briefing per PR — what moved on the thread, the touched story end to end, and changed files that sit off the thread
• Restated-intent detection with graded re-confirm hints
• Optional human-tick gates (offthread_ack / intent_ack) enforced via a specassay/ack commit status

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 (containerized), Spec Kit CLI specify 0.16.3.dev0 (installed from main)

Test project:

• A clean specify init project (install-path evidence: https://github.com/rdryfoos/specassay/blob/main/docs/submission/test-evidence.md)
• HomesFlow, a real example app (https://github.com/rdryfoos/HomesFlow) — real registry, ~81-row trace-manifest

Test scenarios:

1. Added the hosted install-allowed catalogs and installed by ID in a clean project
2. Ran /speckit.specassay-check.gate on a green project (passes, emits manifest)
3. Ran it on a broken thread (refuses, still emits manifest)
4. Live CI demos on the repository: PR Add John Lam as contributor and release badge #1 (green Thread Report), PR Fix release workflow to work with repository rules #2 (refusal), PR doco(spec-driven): Fix small typo in spec-driven.md #4 and feat: implement in Japanese #5 (restated intent)

Example Usage

# Install extension
specify extension add specassay-check --from https://github.com/rdryfoos/specassay/releases/download/v0.3.3/specassay-check-0.3.3.zip

# Use the command (in your integration, e.g. Claude)
/speckit.specassay-check.gate
# → refuses silent gaps; writes trace-manifest.json either way

Proposed Catalog Entry

{
  "specassay-check": {
    "name": "SpecAssay Check",
    "id": "specassay-check",
    "version": "0.3.3",
    "description": "Gate 2 refuses silent gaps and emits a trace-manifest (`trace-manifest.json`).",
    "author": "Rik Dryfoos",
    "download_url": "https://github.com/rdryfoos/specassay/releases/download/v0.3.3/specassay-check-0.3.3.zip",
    "repository": "https://github.com/rdryfoos/specassay",
    "homepage": "https://www.specassay.com",
    "documentation": "https://github.com/rdryfoos/specassay/blob/main/extensions/specassay-check/README.md",
    "license": "MIT",
    "category": "visibility",
    "effect": "read-write",
    "requires": {
      "speckit_version": ">=0.14.0",
      "tools": [
        { "name": "bash", "required": true },
        { "name": "python3", "version": ">=3.8", "required": true }
      ]
    },
    "provides": {
      "commands": 1,
      "hooks": 1
    },
    "tags": ["traceability", "gate", "ci", "governance", "sdd"],
    "verified": false
  }
}

Additional Context

The emitted trace-manifest is deliberately vendor-neutral (format + schemaVersion are the contract); a v5 interop revision is in beta with a second emitter (docs/trace-manifest-v5.md). The walkthrough site (https://www.specassay.com) shows the Gate, the Thread Report, and the intent-PR behavior on live PRs in this repository. Pairs with the specassay preset, which installs the durable-ID contract the Gate enforces.

[github-actions]

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

[github-actions]

Pull request created: #4069

Generated by Add Community Extension from Issue Submission · 302.3 AIC · ⌖ 16.3 AIC · ⊞ 35.3K

[rdryfoos]

done

[KSchlobohm]

Hi @rdryfoos — Copilot found an issue in PR #4069 that blocks review:

The linked submission specifies python3 (>=3.8) as a required tool, but this entry drops the minimum version, making the catalog metadata report older Python 3 installations as compatible. Preserve the submitted version constraint, as other tool entries in this catalog do.
#4069 (comment)

Please reply here when fixed so we can re-check the PR.

[rdryfoos]

Fixed in v0.3.3. extension.yml carried tools: [], so the generated
entry had nothing to carry the constraint. It now declares bash and
python3 >=3.8 in the same shape other catalog entries use, and the
submission and proposed catalog entry match. The floor is deliberate:
the shipped code parses on 3.7, and 3.8 is what is supported and tested.