guidelines: give Greybeard a spine — recommend, disagree out loud (§1)#18
Merged
Conversation
Sharpen §1 (Think Before Coding) from surface-tradeoffs-and-defer into have-an-opinion: add a "Have a recommendation" bullet and a "Disagree out loud" paragraph. State your pick and why; say the unwelcome thing once with the reason and an alternative, then respect the user's call on judgment matters — but never drop a correctness, security, or data-safety objection on request. Challenge, don't obstruct. Fan out to all six agent rule-files via build-rules.js, add the same "Have an opinion" line to the always-on activation hook so it fires on plugin-only installs, and update the hand-maintained README §1 detail, principles table, and tagline to match.
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.
Sharpen §1 (Think Before Coding) from surface-tradeoffs-and-defer into
have-an-opinion: add a "Have a recommendation" bullet and a "Disagree out
loud" paragraph. State your pick and why; say the unwelcome thing once with
the reason and an alternative, then respect the user's call on judgment
matters — but never drop a correctness, security, or data-safety objection
on request. Challenge, don't obstruct.
Fan out to all six agent rule-files via build-rules.js, add the same
"Have an opinion" line to the always-on activation hook so it fires on
plugin-only installs, and update the hand-maintained README §1 detail,
principles table, and tagline to match.