[Preset]: Add OKR Bet Spec Section
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 2/5
- Tempo estimado
- 1-3 horas
- Facilidade para iniciantes
- 15/100
- Tipo de issue
- Funcionalidade
- Clareza
- Razoavelmente clara
- Status de atividade
- Ativa
- Stack de tecnologia
- markdown, yaml
- Domínio
- tooling
Direção de pesquisa
This is a catalog submission for a preset, not a code change: the payload names preset.yml, spec-template.md, speckit.specify.md and a README with an install command. A reviewer would check that the manifest is valid, the README install command works, and the templates apply as described. Done means a maintainer decision on the catalog entry, so a first-time contributor should expect to wait on review rather than write code.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Preset ID
okr-bet
Preset Name
OKR Bet Spec Section
Version
0.2.1
Description
Adds a Hypothesis & Bet section (with the bet's verification contract) to every spec and teaches /speckit.specify to fill it from an okr:/H-n bet. Companion of the okr extension.
Author
juanl
Repository URL
https://github.com/juanl/spec-kit-okr
Download URL
https://github.com/juanl/spec-kit-okr/releases/download/v0.2.1/spec-kit-okr-bet-preset-0.2.1.zip
Documentation URL
https://github.com/juanl/spec-kit-okr/blob/v0.2.1/README.md#install
License
MIT
Required Spec Kit Version
=0.9.0
Required Extensions (optional)
okr (recommended companion: the preset reads the bet file the extension writes; without an okr: token in the feature description it removes the section, so specs without a bet are unchanged)
Templates Provided
- spec-template.md — appends a Hypothesis & Bet section: bet link, hypothesis, KR moved, refutation criterion, validation slice, gated scale stories, guardrails, and the verification contract table (strategy: append)
Commands Provided
- speckit.specify.md — appended instructions: when the description has an
okr:<team>/H-ntoken, fill the section from the bet file, copy the verification contract, make P1 the validation slice, tag success criteria with contract IDs, and add requirements for numbers that cannot be measured yet (strategy: append)
Number of Scripts (optional)
Tags
okr, hypothesis, spec-template, metrics
Key Features
- Composes with any spec template and
/speckit.specify(bothappend), so it replaces nothing - Every spec states the hypothesis it tests, the KR it should move, and what would refute it
- The bet's verification contract is copied into the spec, so success criteria reference the same numbers and thresholds the post-launch review reads
- P1 is written as the validation slice; scale stories are marked as built only if the hypothesis is validated
- Numbers that cannot be read yet (
instrument,blocked,unknown) become functional requirements or dependencies in the validation slice - Specs without an
okr:token come out exactly as before (the section is removed) - Enabling work (
okr:<team>/enabling:<id>) gets a short "Protects" statement instead of a hypothesis
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.ymlmanifest included - Linked README (Documentation URL) explains how to use this preset and includes a valid
specify preset add ...command (preferablyspecify 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)
Testing Details
- Installed with
specify preset add --from <download URL>in a fresh Spec Kit 0.16.2 project (macOS), and with--devin CI (Ubuntu);specify preset resolve spec-templateshows the okr-bet layer, and the generatedspeckit-specifyskill includes the appended instructions - Used with the okr extension on the repo example and on a private project with a real team's bet:
/speckit.specify okr:<team>/H-1 …produced the section with the contract, P1 as the validation slice, and success criteria tagged to contract IDs
Additional Context
Submitted together with the okr extension: #5408.
- Linguagem predominante
- Python
- Estrelas
- 149k
- Forks
- 13.4k
- Merge médio
- 1d 5h
- PRs com merge (30d)
- 223
Preparar o ambiente
Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.
- Sem Dockerfile nem arquivo Docker Compose
- Tem um modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de github/spec-kit
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
Mantenedores costumam responder em até 1 dia
-
triage-must-have
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 78/100
Mantenedores costumam responder em até 1 dia
-
Workflow-step verifier test fixture breaks when the checkout path contains whitespace (4 failures on macOS)Talvez já em andamento @mehdikarimi55 assumiu há 3 dias. Abertatriage-can-wait
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 83/100
Mantenedores costumam responder em até 1 dia
-
Parity tests fail under the documented direct pytest invocation when the ambient python3 lacks PyYAML (11 failures)Talvez já em andamento @mehdikarimi55 assumiu há 3 dias. Abertatriage-must-have
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
Mantenedores costumam responder em até 1 dia
-
bug triage-out-of-scope
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 64/100
Mantenedores costumam responder em até 1 dia
Todas as issues de github/spec-kit
Issues semelhantes
-
bug
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 80/100
glossyio/traffic-monitor#312 ·
Mantenedores costumam responder em até 1 dia
-
local devenv exampleAbertadocumentation enhancement
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 76/100
es-ude/elastic-ai.creator#1046 ·
Mantenedores costumam responder em até 3 dias
-
ENH: permit cachetools >= 7Abertafeature request
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 65/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 72/100
confident-ai/deepteam#306 ·
Mantenedores costumam responder em até 1 dia
-
SslLibrary crashes with unhandled OSError: port/proto not found on non-standard SSL portsTalvez já em andamento @himanchalkaushale assumiu hoje. Aberta
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 82/100
OWASP/Nettacker#1884 · 1 comentário ·
Mantenedores costumam responder em até 1 dia