fix(agent): anchor the narration preamble rule#313
Merged
Conversation
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.
Summary
Replace the vague "say what you are about to do before you begin" narration rule with Claude Code's concrete anchor — state intent before the first tool call, plus short updates at key moments (a load-bearing find, a direction change, progress without a recent update).
Dogfood-surfaced: gpt-5.2 read files silently before acting under the old wording. Fable design-eyeballed (over-narration risk low; the new wording scopes narration more tightly, and Claude Code runs the same phrasing on Claude without over-narrating).