[Preset]: Add specassay

[rdryfoos]

Preset ID

specassay

Preset Name

SpecAssay

Version

0.3.4

Description

Appends durable-ID, Carries, and SpecAssay vocabulary onto Spec Kit spec, tasks, and constitution templates.

Author

Rik Dryfoos

Repository URL

https://github.com/rdryfoos/specassay

Download URL

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

Documentation URL

https://github.com/rdryfoos/specassay/blob/main/presets/specassay/README.md

License

MIT

Required Spec Kit Version

=0.14.0

Required Extensions (optional)

No response

Templates Provided

• spec-template.md — append: inherited durable IDs (US-/FR-/NFR-/AC-) and a risk table traced to FR/AC IDs
• tasks-template.md — append: Carries: required on every task
• constitution-template.md — append: End-to-End Traceability article and the SpecAssay vocabulary

Commands Provided

None

Number of Scripts (optional)

No response

Tags

traceability, durable-ids, governance, sdd

Key Features

• Durable IDs minted once at spec time and inherited downstream, never re-derived
• Carries: marks connect every open task to the intent it serves
• Constitution vocabulary article is self-sufficient (maker's mark/@Covers, Carries:, anointed backlog rows)
• Pure append strategy — layers onto stock Spec Kit templates without replacing the workflow
• Pairs with the specassay-check extension, which enforces this contract at the Gate

Testing Checklist

• Preset installs successfully via specify preset add
• Template resolution works correctly after installation
• Documentation is complete and accurate
• Tested on at least one real project

Submission Requirements

• Valid preset.yml manifest included
• Linked README (Documentation URL) explains how to use this preset and includes a valid specify preset add ... command (preferably specify preset add --from <download-url> using the exact download URL)
• LICENSE file included
• GitHub release created with version tag
• Preset ID follows naming conventions (lowercase-with-hyphens)

[github-actions]

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

[github-actions]

Pull request created: #4070

Generated by Add Community Preset from Issue Submission · 324.8 AIC · ⌖ 16.6 AIC · ⊞ 36.2K

[rdryfoos]

done

[KSchlobohm]

@rdryfoos, thanks for updating the author metadata and publishing the new assets. One preset-specific issue remains before we can refresh the generated PR.

Issue #4058 and preset.yml declare preset version 0.2.1, but the download URL points to the v0.3.2 GitHub release. The preset submission workflow requires a GitHub release matching the submitted preset version, and there is currently no v0.2.1 release. Copilot flagged this mismatch on #4070.

Please either publish the preset asset under a v0.2.1 release and update the download URL, or align the preset manifest, asset, submission, and bundle reference to version 0.3.2. Once updated, let us know here so we can refresh the generated PR.

The other Copilot findings on #4070 concern catalog and documentation ordering; those are maintainer-side changes and require no action from you.

[rdryfoos]

Fixed in v0.3.3, taking the second option: all three components now share
the bundle's version, so the release tag always matches every component
version. The preset is 0.3.3, published as
specassay-preset-0.3.3.zip in the v0.3.3 release, and the bundle
reference is updated to match. Component versions will move together from
here, so this cannot drift again.

[KSchlobohm]

Thanks for aligning the release, preset manifest, and bundle at v0.3.3. One reference still needs updating: the preset README’s install command points to v0.3.1/specassay-preset-0.2.0.zip.

Please update it to:
https://github.com/rdryfoos/specassay/releases/download/v0.3.3/specassay-preset-0.3.3.zip

Once updated, let us know so we can regenerate the catalog PR.

[rdryfoos]

Fixed in v0.3.4. The preset README shipped inside the preset zip still
pointed at the v0.3.1 asset name through the last two bumps; that file
wasn't in either sweep's grep pattern. It now points at v0.3.4, and
since the fix lives inside the artifact rather than just the issue
text, this went out as a real release, not an edit.