[Preset]: Add OKR Bet Spec Section
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 15/100
- Tipo di issue
- Funzionalità
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- markdown, yaml
- Ambito
- tooling
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- Python
- Stelle
- 149k
- Fork
- 13.4k
- Merge medio
- 1g 5h
- PR unite (30g)
- 223
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di github/spec-kit
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
triage-must-have
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Workflow-step verifier test fixture breaks when the checkout path contains whitespace (4 failures on macOS)Forse già presa @mehdikarimi55 l’ha presa 3 giorni fa. Apertatriage-can-wait
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
I maintainer di solito rispondono entro 1 giorno
-
Parity tests fail under the documented direct pytest invocation when the ambient python3 lacks PyYAML (11 failures)Forse già presa @mehdikarimi55 l’ha presa 3 giorni fa. Apertatriage-must-have
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
bug triage-out-of-scope
Difficoltà 2/5 1-3 ore Idoneità per principianti 64/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di github/spec-kit
Issue simili
-
SslLibrary crashes with unhandled OSError: port/proto not found on non-standard SSL portsForse già presa @himanchalkaushale l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
OWASP/Nettacker#1884 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
A-connection-core C-enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 88/100
aws-samples/sample-per-model-bedrock#869 ·
I maintainer di solito rispondono entro 1 giorno
-
Spec: say that included_antigen_sources gates LENS labels; do not merge it into antigen kindsAperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
fzn0x/watchtower#17 ·