Add Spec Trace extension to community catalog by Quratulain-bilal · Pull Request #2527 · github/spec-kit

Quratulain-bilal · 2026-05-12T08:53:17Z

Adds Spec Trace to the community catalog — a build-time requirement → test traceability extension.

/speckit.trace.build parses spec.md for REQ-XXX tokens and the test suite for the same tokens, then writes
.specify/trace.md containing a coverage matrix. Companion commands:

/speckit.trace.gaps — list requirements with zero matching tests
/speckit.trace.orphans — list tests that do not anchor to any REQ
/speckit.trace.report — human-readable summary

Effect is Read+Write (because trace.build writes .specify/trace.md).

Changes

extensions/catalog.community.json — new "trace" entry, alphabetically placed between token-analyzer and
v-model.
docs/community/extensions.md — new row added alphabetically between Spec Sync and Spec Validate. The public
community extensions table lives here per the repo convention documented in
.github/skills/add-community-extension/SKILL.md (lines 104-108). README.md is intentionally not touched — the old table
there has been migrated.

Extension repo

Source: https://github.com/Quratulain-bilal/spec-kit-trace
Release: https://github.com/Quratulain-bilal/spec-kit-trace/releases/tag/v1.0.0
License: MIT

Verification

python -m json.tool extensions/catalog.community.json passes — valid JSON.
Row position confirmed alphabetical against neighbours in both catalog.community.json and
docs/community/extensions.md.
Extension installs cleanly via specify extension add trace --from <release-url>; all four commands execute without
errors against a project with spec.md containing REQ-XXX tokens.
Effect column matches actual behavior (Read+Write, since trace.build writes .specify/trace.md).

Review feedback addressed

All Copilot review notes are addressed in the commit history on this branch:

Read-only vs Read+Write (Copilot comments on README.md:276 and README.md:278) — fixed in 0679e73 (catalog
Effect column flipped to Read+Write).
Missing row in docs/community/extensions.md (Copilot comment on extensions/catalog.community.json:2952) — fixed
in 0a5482b (row added alphabetically between Spec Sync and Spec Validate).
PR description pointed at README instead of docs/ (Copilot comment on docs/community/extensions.md:104) — fixed
in this body update (the "Changes" section now correctly names docs/community/extensions.md and explicitly notes README
is intentionally untouched).

For future submissions I will use the Extension Submission issue template up-front, per @mnriem's note on the initial
review.

mnriem

Please resolve conflicts

Note going forward adding/updating an extension please create an issue using the 'Extension Submission' template.

Copilot

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 trace entry to extensions/catalog.community.json (including metadata, tags, and download URL) and bumped the catalog updated_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

mnriem · 2026-05-12T16:14:14Z

Please address Copilot feedback

Quratulain-bilal · 2026-05-13T02:36:39Z

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 .

Copilot

Copilot's findings

Files reviewed: 2/2 changed files
Comments generated: 1

mnriem · 2026-05-13T13:38:38Z

Please address Copilot feedback

The /speckit.trace.build command writes .specify/trace.md, so the catalog row's Effect column was wrong. Aligning with the extension's documented behavior.

Copilot

Copilot's findings

Files reviewed: 2/2 changed files
Comments generated: 0 new

# Conflicts: # README.md

Copilot

Copilot's findings

Files reviewed: 1/1 changed files
Comments generated: 1

mnriem · 2026-05-14T20:13:32Z

Please address Copilot feedback. Note that huge table of community extensions in the README.md has moved to docs/community/extensions.md hence why it is asking you to list it there

The public community extensions table moved from README.md to docs/community/extensions.md per the repo convention documented in .github/skills/add-community-extension/SKILL.md. Adding the Spec Trace row alphabetically between Spec Sync and Spec Validate so the doc stays in sync with the catalog entry already added.

Copilot

Copilot's findings

Files reviewed: 2/2 changed files
Comments generated: 1

mnriem · 2026-05-15T21:32:32Z

Please address Copilot feedback

# Conflicts: # extensions/catalog.community.json

Quratulain-bilal · 2026-06-03T02:45:29Z

@mnriem all three Copilot notes are addressed on the current head (0a5482b):

Effect column corrected to Read+Write in 0679e73 (catalog) — matches trace.build writing .specify/trace.md.
docs/community/extensions.md row added in 0a5482b, alphabetically between Spec Sync and Spec Validate, so the public
table stays in sync with the catalog JSON.
PR description updated above to point at docs/community/extensions.md instead of the migrated README table.

Apologies for missing the Extension Submission template on the initial submission I'll use it for all future
catalog entries.

Ready for another pass whenever you have a moment 🙏

Copilot

Copilot's findings

Files reviewed: 2/2 changed files
Comments generated: 1

Copilot's review on this PR noted that the Spec Trace entry was the only one in catalog.community.json using JSON Unicode escape sequences (\u2192 for the arrow, \u2014 for the em-dash). Every other entry that uses those characters writes them as literal multi-byte UTF-8 (18 entries with literal em-dash, 5 with literal arrow), so the escaped form made this row harder to read and review in plain text and stood out as the only inconsistency in the file. Replacing the escapes with the literal characters keeps the entry visually consistent with the rest of the catalog and decodes to the same string at runtime, so no consumer changes.

Add Spec Trace extension to community catalog

b0061b3

Quratulain-bilal requested a review from mnriem as a code owner May 12, 2026 08:53

mnriem requested a review from Copilot May 12, 2026 14:02

Copilot started reviewing on behalf of mnriem May 12, 2026 14:03 View session

mnriem requested changes May 12, 2026

View reviewed changes

Copilot AI reviewed May 12, 2026

View reviewed changes

Comment thread README.md Outdated

Merge remote-tracking branch 'origin/main' into feat/trace-extension

71300c4

mnriem requested a review from Copilot May 13, 2026 12:43

Copilot started reviewing on behalf of mnriem May 13, 2026 12:44 View session

Copilot AI reviewed May 13, 2026

View reviewed changes

Comment thread README.md Outdated

docs(catalog): mark Spec Trace as Read+Write

0679e73

The /speckit.trace.build command writes .specify/trace.md, so the catalog row's Effect column was wrong. Aligning with the extension's documented behavior.

mnriem requested a review from Copilot May 14, 2026 13:22

Copilot started reviewing on behalf of mnriem May 14, 2026 13:22 View session

Copilot AI reviewed May 14, 2026

View reviewed changes

Merge remote-tracking branch 'origin/main' into feat/trace-extension

197af20

# Conflicts: # README.md

mnriem requested a review from Copilot May 14, 2026 19:27

Copilot started reviewing on behalf of mnriem May 14, 2026 19:27 View session

Copilot AI reviewed May 14, 2026

View reviewed changes

Comment thread extensions/catalog.community.json

mnriem requested a review from Copilot May 15, 2026 13:01

Copilot started reviewing on behalf of mnriem May 15, 2026 13:01 View session

Copilot AI reviewed May 15, 2026

View reviewed changes

Comment thread docs/community/extensions.md

Merge remote-tracking branch 'origin/main' into feat/trace-extension

388aa46

# Conflicts: # extensions/catalog.community.json

mnriem requested a review from Copilot June 3, 2026 13:50

Copilot started reviewing on behalf of mnriem June 3, 2026 13:50 View session

Copilot AI reviewed Jun 3, 2026

View reviewed changes

Comment thread extensions/catalog.community.json Outdated

Conversation

Quratulain-bilal commented May 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Changes

Extension repo

Verification

Review feedback addressed

Uh oh!

mnriem left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Copilot's findings

Uh oh!

Uh oh!

mnriem commented May 12, 2026

Uh oh!

Quratulain-bilal commented May 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot's findings

Uh oh!

Uh oh!

mnriem commented May 13, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot's findings

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot's findings

Uh oh!

Uh oh!

mnriem commented May 14, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot's findings

Uh oh!

Uh oh!

mnriem commented May 15, 2026

Uh oh!

Quratulain-bilal commented Jun 3, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot's findings

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Quratulain-bilal commented May 12, 2026 •

edited

Loading

Quratulain-bilal commented May 13, 2026 •

edited

Loading