Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Preset]: Add SpecAssay (update to 0.5.2)

Abierto Apto para principiantes
#4,713 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
75/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Área
tooling

Línea de trabajo

The issue is about adding a preset to the Spec Kit repository. Look at the preset.yml manifest format and existing presets in the repository. The preset files are provided via a download URL; the task is to integrate this preset into the project's preset listing. Check the repository's documentation on how presets are added and validated. The work involves updating the preset registry or documentation to include SpecAssay v0.5.2.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

preset-submission triage-must-have validation-passed
Preset ID

specassay

Preset Name

SpecAssay

Version

0.5.2

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.2/specassay-preset-0.5.2.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)

specassay-check (>=0.5.2) - optional. The preset writes the vocabulary; the extension enforces it. The templates are useful without it, but nothing refuses a silent gap until the extension is installed.

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

Update to an existing entry. Replaces #4691 which was filed at 0.5.1 before v0.5.2 shipped.

Tested on Spec Kit 1.0.5, Linux, 2026-09-23, against the published v0.5.2 asset:

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

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

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

sha256, computed from the published v0.5.2 assets on 2026-09-23:
9920daf8b7ebe2d5e0d5e723409719afeaaa7c59788a6f3ecda67e2f7543d0b9 specassay-preset-0.5.2.zip

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)
Lenguaje dominante
Python
Estrellas
138k
Forks
12.4k
Merge medio
3 d 4 h
PR fusionados (30 d)
154

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/spec-kit

Todos los issues de github/spec-kit

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.