Add Spec Trace extension to community catalog#2527
Open
Quratulain-bilal wants to merge 2 commits into
Open
Conversation
mnriem
requested changes
May 12, 2026
Collaborator
mnriem
left a comment
mnriem
left a comment
There was a problem hiding this comment.
Please resolve conflicts
Note going forward adding/updating an extension please create an issue using the 'Extension Submission' template.
Contributor
There was a problem hiding this comment.
Pull request overview
Adds the Spec Trace community extension to Spec Kit’s discovery surfaces (community catalog JSON + README table), making it easier for users to find and reference the extension for requirement→test traceability reporting.
Changes:
- Added a new
traceentry toextensions/catalog.community.json(including metadata, tags, and download URL) and bumped the catalogupdated_at. - Added a new “Spec Trace” row to the README Community Extensions table in alphabetical order.
Show a summary per file
| File | Description |
|---|---|
| README.md | Adds the “Spec Trace” entry to the Community Extensions table. |
| extensions/catalog.community.json | Adds the trace extension metadata and updates updated_at. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 1
| | Spec Refine | Update specs in-place, propagate changes to plan and tasks, and diff impact across artifacts | `process` | Read+Write | [spec-kit-refine](https://github.com/Quratulain-bilal/spec-kit-refine) | | ||
| | Spec Scope | Effort estimation and scope tracking — estimate work, detect creep, and budget time per phase | `process` | Read-only | [spec-kit-scope-](https://github.com/Quratulain-bilal/spec-kit-scope-) | | ||
| | Spec Sync | Detect and resolve drift between specs and implementation. AI-assisted resolution with human approval | `docs` | Read+Write | [spec-kit-sync](https://github.com/bgervin/spec-kit-sync) | | ||
| | Spec Trace | Build a requirement → test traceability matrix from spec.md and the test suite — surface untested requirements and orphan tests | `process` | Read-only | [spec-kit-trace](https://github.com/Quratulain-bilal/spec-kit-trace) | |
Collaborator
|
Please address Copilot feedback |
Contributor
Author
|
Conflicts resolved in 71300c4 clean diff now (README +1, catalog +32). Thank you for the heads-up about the Extension Submission template I'll absolutely follow that process for all future extensions and updates going forward. Sorry for the extra work this caused; I appreciate the patience . |
| | Spec Refine | Update specs in-place, propagate changes to plan and tasks, and diff impact across artifacts | `process` | Read+Write | [spec-kit-refine](https://github.com/Quratulain-bilal/spec-kit-refine) | | ||
| | Spec Scope | Effort estimation and scope tracking — estimate work, detect creep, and budget time per phase | `process` | Read-only | [spec-kit-scope-](https://github.com/Quratulain-bilal/spec-kit-scope-) | | ||
| | Spec Sync | Detect and resolve drift between specs and implementation. AI-assisted resolution with human approval | `docs` | Read+Write | [spec-kit-sync](https://github.com/bgervin/spec-kit-sync) | | ||
| | Spec Trace | Build a requirement → test traceability matrix from spec.md and the test suite — surface untested requirements and orphan tests | `process` | Read-only | [spec-kit-trace](https://github.com/Quratulain-bilal/spec-kit-trace) | |
Collaborator
|
Please address Copilot feedback |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new community extension Spec Trace to
catalog.community.jsonand the README community-extensions table.Spec Trace builds a requirement → test traceability matrix from
spec.mdand the test suite. It surfaces untestedrequirements (
/speckit.trace.gaps), orphan tests whoseREQ-XXXIDs no longer exist in the spec(
/speckit.trace.orphans), and produces a compact CI-friendly compliance report (/speckit.trace.report).Why this fills a gap
Spec Kit treats
spec.mdas the source of truth, but nothing in the default workflow links a requirement to the teststhat prove it works. Coverage tools measure lines of code, not behaviour described in the spec. This extension closes
that loop — turning
REQ-XXXidentifiers in spec and tests into a deterministic matrix that CI can gate on.Extension details
build,gaps,orphans,report)/speckit.trace.buildwrites, and only to.specify/trace.mdREQ-XXXtokens in any test file (Python, JS/TS, Go, generic)Changes
extensions/catalog.community.jsonnewtraceentry placed alphabetically; top-levelupdated_atbumped to2026-05-12
README.mdnewSpec Tracerow placed alphabetically between Spec Sync and Spec Validate