Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

[Preset]: Add Agentstandards Task Gate

Fechada
  • Algo errado?
#4,721 5 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 2 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
45/100
Tipo de issue
Funcionalidade
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
python
Domínio
cli, tooling

Direção de pesquisa

The issue is about adding a new preset to Spec Kit that wraps the speckit.tasks command with a gate check. Start by examining the preset system in the repository, likely in a presets/ directory or related to command wrapping. Look for how existing presets are structured and how commands are extended. The new preset must integrate with the 'agentstandards' extension and perform an offline gate check. Testing involves verifying the preset installs and the wrapper command works as described.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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

agentstandards-gate

Preset Name

Agentstandards Task Gate

Version

0.1.1

Description

Hard-blocks Spec Kit task generation until the persisted multi-vendor architecture gate is READY.

Author

bbjwz

Repository URL

https://github.com/bbjwz/agentstandards

Download URL

https://github.com/bbjwz/agentstandards/releases/download/v0.1.1/agentstandards-gate-0.1.1.zip

Documentation URL

https://github.com/bbjwz/agentstandards/blob/v0.1.1/presets/agentstandards-gate/README.md

License

MIT

Required Spec Kit Version

=1.0.8,<2.0.0

Required Extensions (optional)

agentstandards

Templates Provided

None; this is a command-only wrapping preset.

Commands Provided
  • speckit.tasks.md - wraps the core speckit.tasks command and runs the persisted Agentstandards READY-gate check first.
Number of Scripts (optional)

0

Tags

architecture, gate, multi-vendor, tasks

Key Features
  • Enforces the architecture council between planning and task generation.
  • Performs an offline, deterministic gate check before speckit.tasks.
  • Blocks missing, stale, invalid, or non-READY aggregate gate artifacts.
  • Preserves the core Spec Kit task command through the wrap strategy.
  • Keeps paid model calls out of normal task-gate verification.
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)
Additional Testing Details

Tested in clean Spec Kit 1.0.8 and 1.0.10 Codex projects. The v0.1.1 release manifest declares requires.extensions: [agentstandards]. Installing the preset without the extension now succeeds with an explicit warning that agentstandards is not installed and gives the corrective specify extension add agentstandards command.

The release archive installed successfully with:

specify preset add \
  --from https://github.com/bbjwz/agentstandards/releases/download/v0.1.1/agentstandards-gate-0.1.1.zip

The installed preset resolves its speckit.tasks wrapper correctly. Automated tests cover READY, blocked, stale, disagreement, invalid-manifest, and explicit-human-exception gate states. Release artifacts include SHA-256 checksums and GitHub build-provenance attestations.

SHA-256

9b61a7fffbe8f0de61ab44ac20844b24e60dc543882240d826423e48fa5bd9bb

Linguagem predominante
Python
Estrelas
138k
Forks
12.4k
Merge médio
2d 11h
PRs com merge (30d)
163

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de github/spec-kit

Todas as issues de github/spec-kit

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.