Repository navigation
feat: port Spec Kit workflow preset - #28
Merged
Merged
Conversation
Port the preset to the approved RFC-backed lifecycle with\ncommand-aligned artifacts, reviewed task packages, and isolated\npacket execution.\n\nRemove the legacy protocol, analysis surface, and compatibility\npreflight rather than retaining incompatible migration paths.
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
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.
📝 Summary
Replace the hybrid Spec Kit preset with the approved 0.3.0 RFC-backed lifecycle.
The preset now owns feature-definition convergence, reviewed RFC planning, immutable execution packages, and isolated packet execution.
It removes the incompatible analysis surface and command-time compatibility preflight instead of migrating legacy artifacts.
Key Decisions
🔄 Command-Aligned Lifecycle
Replace the five stock workflow surfaces and three core templates so each phase has one authoritative artifact, explicit review boundary, and human gate.
🔒 Isolated Packet Execution
Use provider-neutral sub-plans, local runtime progress, protected feature baselines, and policy-preserving packet integration so workers cannot alter planning authority or the active branch directly.
🧹 Legacy Protocol Removal
Remove the analysis, execution-plan, protocol-compatibility, and optional-review artifacts. Existing runs are intentionally not migrated and must be completed or abandoned before refresh.
🔄 Before & After