Repository navigation
feat: add guided review to Spec Kit preset - #26
Merged
Merged
Conversation
Offer decision-focused walkthroughs after specification and planning while preserving phase ownership and upstream command behavior. Bump the preset to 0.2.0 and keep the execution-plan protocol at 0.1.0.
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
Generated specification and planning artifacts were difficult to validate without rereading every file.
This adds optional, decision-focused walkthroughs after specification and planning while preserving independent review and normal handoffs.
The preset advances to 0.2.0 without changing execution-plan protocol 0.1.0.
Key Decisions
🧭 Shared Human Review Protocol
A shared protocol keeps walkthroughs optional, cognitively small, and focused on consequential decisions rather than literal file sections. Settled feedback updates and revalidates current-phase artifacts before the walkthrough continues.
🔒 Phase Ownership
Planning treats the accepted specification as its authoritative baseline. The planning walkthrough reviews only technical decisions introduced or derived during planning, preventing requirements from being reopened unless a concrete blocker belongs to an earlier workflow.
🔁 Upstream Composition
Specification and planning remain wrappers around stock Spec Kit commands. Final reports and handoffs are deferred until the review is completed or declined, while generation, validation, and mandatory hooks retain their upstream behavior.
✅ Contract Validation
Deterministic checks cover command composition, package inventory, review behavior, phase ownership, and the preset/protocol version boundary. Temporary installation verifies that Spec Kit materializes the wrapped commands with project-relative references.
🔄 Before & After