sprint-plan: revise Phase 2 wording to acknowledge feasibility-gate skip in lean/solo#89
Open
specterslient95-lgtm wants to merge 1 commit into
Conversation
…kip in lean/solo Phase 2 claimed the producer feasibility gate (Phase 4) "runs first" before the plan file is written, but Phase 4 itself skips that gate in lean and solo modes. Following Phase 2 verbatim, the plan reaches write approval without the promised feasibility review in two of the three modes. Update Phase 2 to spell out the mode-dependent flow: full -> Phase 4 runs first; lean/solo -> Phase 4 is skipped per its own block and the user takes the feasibility responsibility at the write step.
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.
Fixes #88.
Phase 2 said the producer feasibility gate (Phase 4) "runs first"
before the plan is written, but Phase 4 itself skips that gate in
leanandsolomodes. This PR keeps the existing skip behaviourand only adjusts Phase 2's wording so the mode-dependent flow is
explicit:
full-> Phase 4 runs first;lean/solo-> Phase 4is skipped, and the user takes feasibility responsibility at the
write-approval step.