[Preset]: Add OKR Bet Spec Section

Offen
  • Stimmt etwas nicht?
#5,409 3 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
2/5
Geschätzter Aufwand
1-3 Stunden
Anfängerfreundlichkeit
15/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
markdown, yaml
Bereich
tooling

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

author-awaiting preset-submission triage-must-have validation-failed
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-n token, 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 (both append), 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.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)
Testing Details
  • Installed with specify preset add --from <download URL> in a fresh Spec Kit 0.16.2 project (macOS), and with --dev in CI (Ubuntu); specify preset resolve spec-template shows the okr-bet layer, and the generated speckit-specify skill 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.

Vorherrschende Sprache
Python
Sterne
149k
Forks
13.4k
Ø Merge
1 T. 5 Std.
Gemergte PRs (30 T.)
223

Entwicklungsumgebung

In Codespaces öffnen

Startet den Dev-Container des Projekts im Browser, mit Ihrem eigenen GitHub-Konto.

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus github/spec-kit

Alle Issues in github/spec-kit

Ähnliche Issues

Weitere Issues zu Python

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.