🤖 Require plain English in architecture and planning roles - #652
Merged
Conversation
PR #652: 🤖 Require plain English in architecture and planning roles2 files, +26 / -0 Scope✅ PR scope looks good. Structural✅ No structural bloat detected. Slop✅ Slop indicators look low. Static Analysis✅ Oxlint found no issues. CorrectnessFILE: .agents/architect.md FILE: .agents/planner.md |
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.
Why
Architecture reviews and implementation plans are easier to act on when they
state the practical result in familiar language. The role contracts currently
define what the Architect and Planner must decide, but they do not explicitly
define how those decisions should be communicated.
What changes
Before:
The Architect and Planner could satisfy their role contracts with dense project
jargon or sentences that made readers unpack several decisions at once.
After:
Both roles default to plain English, lead with the practical result, explain
necessary project terms, and keep exact technical details without making the
reader translate them.
How to verify it
git diff --check -- .agents/architect.md .agents/planner.mdproves the twoinstruction files contain no whitespace errors.
Languagesection and confirm it preserves technical precisionwhile requiring clear, direct wording.
Scope
Included
Intentionally unchanged
technical detail.
Scope confirmation