Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Preset]: Add SpecAssay (update to 0.5.1)

Open Beginner friendly
#4,691 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Domain
tooling

Research direction

Use the existing SpecAssay catalog entry as the starting point; verify the preset.yml manifest, linked README.md, and the three named templates against the 0.5.1 release asset. Run the documented specify preset add and preset list commands, then confirm all three templates resolve and the tasks template retains its Carries vocabulary.

Written by the indexing model from the issue text.

Description

enhancement needs-triage
Preset ID

specassay

Preset Name

SpecAssay

Version

0.5.1

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.5.1/specassay-preset-0.5.1.zip

Documentation URL

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

License

MIT

Required Spec Kit Version

=0.14.0,<2.0.0

Required Extensions (optional)

No response

Templates Provided
  • spec-template.md
  • tasks-template.md
  • constitution-template.md
Commands Provided

0

Number of Scripts (optional)

0

Tags

traceability, durable-ids, governance, sdd

Key Features
  • Spec template inherits durable IDs from the registry rather than inventing new ones per spec
  • Tasks template carries a **Carries**: line, the declaration that binds a task to the IDs it serves
  • Constitution template carries the end-to-end traceability article as a non-negotiable
  • Append strategy at priority 10, so it layers onto stock Spec Kit templates rather than replacing them

This updates the existing catalog entry from 0.4.12 to 0.5.1, superseding
issue #4253 (merged as catalog PR #4256). It replaces #4650, closed by a
maintainer in favour of a clean issue.

Tested on Spec Kit 1.0.5, Linux, 2026-09-20:

$ specify preset add specassay --from https://github.com/rdryfoos/specassay/releases/download/v0.5.1/specassay-preset-0.5.1.zip
Preset 'SpecAssay' v0.5.1 installed (priority 10)

$ specify preset list
SpecAssay (specassay) v0.5.1 - enabled - priority 10
Templates: 3

All three templates resolve, and the tasks template carries its Carries
vocabulary intact after installation.

sha256, re-confirmed against the published asset 2026-09-22:
41e5b5e807bbb2b7d4d90253886122416109465af023d85a110cd522c16848fc specassay-preset-0.5.1.zip

Companion issues: the extension (updates #4252) and the bundle (updates #4255).

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)
Dominant language
Python
Stars
138k
Forks
12.4k
Avg merge
3d 6h
Merged PRs (30d)
145

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/spec-kit

All issues in github/spec-kit

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.