feat(skills): release-planning + issue-driven delivery loop; bump to 0.5.0#79
Merged
Merged
Conversation
… to 0.5.0 Accommodates the issue→loop→release flow observed on synth/kiln/loom and makes release planning live in rivet. Part A — release planning IN rivet: use the existing `release:` field + status lifecycle (draft→…→verified→accepted) to assign which requirements land in which release; readiness is a query (scope all verified + V closed), not a calendar; GitHub milestones become a view, rivet is the source of truth; drive "what's needed for v0.X" from it. Part B — issue-driven delivery loop: error/regression/optimization in → evaluate (measure, don't guess — the synth bar: a regression is a number like 255→257 cycles) → classify (new requirement / regression / optimization) → land in rivet assigned to a release → run the full chain (feature-loop, oracle-gate, proof-synthesis) → close the V (traceability-audit) → ship (release-execution). Worked shapes for optimization (synth/loom), bug (kiln), capability gap. Composes bootstrap-verification, feature-loop, proof-synthesis, traceability- audit, release-execution. Twelfth skill; plugin + marketplace bumped to 0.5.0. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Accommodates the issue→loop→release flow seen on synth/kiln/loom and moves release planning into rivet.
Part A — planning in rivet: uses rivet's existing
release:field + status lifecycle to assign which requirements land in which release; readiness is a query (scope allverified+ V closed), not a calendar; GitHub milestones become a view, rivet is source of truth; drive "what's needed for v0.X" from it.Part B — delivery loop: error/regression/optimization in → evaluate (measure, don't guess — the synth bar: a regression is a number, 255→257 cycles) → classify (new req / regression / optimization) → land in rivet assigned to a release → run the full chain (feature-loop, oracle-gate, proof-synthesis) → close the V (traceability-audit) → ship (release-execution). Worked shapes for optimization (synth/loom), bug (kiln), capability gap (loom).
Twelfth skill; plugin + marketplace → 0.5.0.
🤖 Generated with Claude Code