fix(lfg): enforce plan phase with explicit step gating#231
Merged
kieranklaassen merged 1 commit intoEveryInc:mainfrom Mar 10, 2026
Merged
fix(lfg): enforce plan phase with explicit step gating#231kieranklaassen merged 1 commit intoEveryInc:mainfrom
kieranklaassen merged 1 commit intoEveryInc:mainfrom
Conversation
Add CRITICAL instruction block and GATE checkpoints between steps to prevent Claude from skipping the plan phase and jumping straight to coding. Each gate requires verification that the previous step produced its expected output before proceeding. Closes EveryInc#227 Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
janneaho
approved these changes
Mar 8, 2026
janneaho
left a comment
janneaho
left a comment
There was a problem hiding this comment.
The fix solid, accurate and targeted. Nothing to add, looks good to merge.
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
3 participants
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
/lfgemphasizing that steps must be executed in order and the plan phase must complete before any coding beginsProblem
/lfgwas skipping the plan phase (/ce:plan) and jumping straight to coding. The existing "Run these slash commands in order" instruction was not forceful enough to prevent Claude from bypassing the plan step.Closes #227
Test plan
/lfg "small feature"and verify that/ce:planexecutes and produces a plan file before/ce:workbegins/ce:planfails to produce a plan file, the gate catches it and re-runs the plan stepCo-Authored-By: Claude Opus 4.6 noreply@anthropic.com