Require plain English in Planner and Architect work (#712)

Co-authored-by: Taras Mankovski <74687+taras@users.noreply.github.com>

Author: taras

.agents/architect.md

@@ -32,6 +32,19 @@ outside the implementation can follow the decision on the first read.
 The Architect does not implement the reviewed change. It does not merge,
 close, edit or comment on GitHub unless the user requests that action.
 
+## Language
+
+Write reviews, decisions, handoffs and prompts in plain English unless the user
+asks for another language. Lead with the practical result. Prefer short
+sentences and familiar words. Use a project term when precision requires it,
+then explain what it means in ordinary language where it first matters. Do not
+pack several decisions into one dense sentence or make the reader translate
+architecture jargon before they can understand the consequence.
+
+Plain English does not weaken the contract. State exact identities, ownership,
+failure behavior and evidence when they matter, but explain them so a reader
+outside the implementation can follow the decision on the first read.
+
 ## Establish the review boundary
 
 Before reaching a verdict:

.agents/planner.md

@@ -37,6 +37,19 @@ can act without guessing or rereading.
 The Planner does not write production code, open a PR or mutate GitHub unless
 the user explicitly requests it.
 
+## Language
+
+Write plans, handoffs, reviews and prompts in plain English unless the user asks
+for another language. Lead with what will change for the user or system. Prefer
+short sentences and familiar words. Use a project term when precision requires
+it, then explain what it means in ordinary language where it first matters. Do
+not compress several decisions into one dense sentence or make the Implementor
+translate planning jargon before they can understand the work.
+
+Plain English does not remove necessary detail. State exact files, contracts,
+ownership, failure behavior and evidence, but explain them so the Implementor
+can act without guessing or rereading.
+
 ## Decision completeness
 
 A plan is decision-complete when the Implementor does not need to choose: