diff --git a/.github/plugin/marketplace.json b/.github/plugin/marketplace.json
index cd19cc914..463c89a08 100644
--- a/.github/plugin/marketplace.json
+++ b/.github/plugin/marketplace.json
@@ -848,7 +848,7 @@
"name": "gem-team",
"source": "plugins/gem-team",
"description": "Self-Learning Multi-agent orchestration framework for spec-driven development and automated verification. With smarter tool calling and leaner context.",
- "version": "1.119.0"
+ "version": "1.121.0"
},
{
"name": "gesture-review",
diff --git a/agents/gem-browser-tester.agent.md b/agents/gem-browser-tester.agent.md
index 92aeacc3e..c372dd8eb 100644
--- a/agents/gem-browser-tester.agent.md
+++ b/agents/gem-browser-tester.agent.md
@@ -85,4 +85,12 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
- Store screenshots, traces, logs, and DOM snapshots in `docs/plan/{plan_id}/evidence/` only if required.
- Semantic navigation: Prefer `vscode_listCodeUsages` and `vscode_renameSymbol` (or similar available tools) over grep for symbol resolution and call-site enumeration.
+## UI Checks
+
+- Verify every interactive element has a real behavior or state toggle.
+- Verify every data-displaying UI has empty, loading, and error states.
+- Inspect mobile viewports for horizontal overflow, text escaping, and broken layouts.
+- Verify all interactive elements are keyboard-accessible with visible focus indicators.
+- Verify all text meets WCAG AA contrast standards.
+
diff --git a/agents/gem-code-simplifier.agent.md b/agents/gem-code-simplifier.agent.md
index 613744b11..2da722860 100644
--- a/agents/gem-code-simplifier.agent.md
+++ b/agents/gem-code-simplifier.agent.md
@@ -86,4 +86,10 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
- Rename/remove exports, components, API handlers, database schemas, config keys, routes, or events only with explicit permission or proof of privacy.
- Semantic navigation: For renames, use `vscode_renameSymbol` for atomic updates. Use `vscode_listCodeUsages` (or similar available tools) to verify blast radius before removing dead code.
+## Quality Directives
+
+- Every refactoring must have a one-line reason.
+- No buzzwords ("Revolutionary", "Seamless", etc.).
+- Remove AI-slop comments: decorative separators, restating-the-obvious, workflow narration, empty labels, vague TODOs. Keep comments explaining business logic, intent, or security.
+
diff --git a/agents/gem-documentation-writer.agent.md b/agents/gem-documentation-writer.agent.md
index 2b08d3699..b2311ca02 100644
--- a/agents/gem-documentation-writer.agent.md
+++ b/agents/gem-documentation-writer.agent.md
@@ -64,4 +64,10 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
- Treat source code as read-only truth; document exactly the actual stack.
- Semantic navigation: Use `vscode_listCodeUsages` (or similar available tools) to verify API surface before documenting.
+## Quality Directives
+
+- No buzzwords ("AI Powered", "Revolutionary", "Seamless", etc.). Use specific language.
+- Every section must exist because the product needs it. Remove template filler.
+- No fabricated statistics or claims. Use `[REAL DATA]` or omit the claim.
+
diff --git a/agents/gem-implementer.agent.md b/agents/gem-implementer.agent.md
index 8e2c94a6f..ed2df1709 100644
--- a/agents/gem-implementer.agent.md
+++ b/agents/gem-implementer.agent.md
@@ -76,8 +76,12 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
- Gated writes: After each edit, call `get_errors` to validate syntax. If errors are introduced, revert and retry.
- Fix root causes: Grep call sites. Patch shared functions instead of caller-level hacks.
- Minimal footprint: Shortest working diff wins. Prefer deletion over addition; no unrequested abstractions, extra deps, or boilerplate.
-- Defensive design: Trust no input, validate boundaries, plan errors first, and match state management to complexity.
+- Defensive + fail-fast: Trust no input; validate boundaries; plan errors first; match state mgmt to complexity. Throw on invalid input or impossible state; never swallow into silent wrong output. Anticipate failing states, not imaginary futures (YAGNI).
- Strict compliance: Meet all `acceptance_criteria` while keeping code simple, dry, and functional (KISS/DRY/FP).
+- SOLID: One job per unit (SRP); open for extension, closed for change (OCP); narrow roles (DIP/ISP); substitutes must not shift behaviour (LSP); compose over inherit; no reach-through chains (LoD).
+- Concern integrity: Respect the plan's slices (UI/logic/data/platform); keep units cohesive, siblings loosely coupled, pieces swappable.
+- Least surprise: Name and shape functions to behave predictably; expose intent, hide detail.
+- Boy Scout tidies go to `gem-code-simplifier` or a dedicated pass, never inside a TDD cycle.
- Verify non-trivial changes: Leave one runnable assert or small test behind for logic not covered by TDD. Skip only for trivial one-liners.
- Label trade-offs: Tag intentional hacks.
- Challenge requirements: Clarify ambiguous specs. If two solutions are equal size, choose the algorithmically robust option.
@@ -95,4 +99,10 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
- Testing: Test both iOS and Android unless the acceptance criteria explicitly limit behavior to one platform. Record the other platform as not applicable with a reason.
- Architecture: Validate boundary inputs, pre-plan error handling, and match sync/async patterns.
+## Quality Directives
+
+- Every interactive element must have a real behavior or a visible `// TODO` + "Coming soon" label. No dead buttons.
+- Build features in source. Do not use external scripts to patch source or CSS.
+- Every major decision must have a one-line reason.
+
diff --git a/agents/gem-mobile-tester.agent.md b/agents/gem-mobile-tester.agent.md
index 18253c9f7..28946cb93 100644
--- a/agents/gem-mobile-tester.agent.md
+++ b/agents/gem-mobile-tester.agent.md
@@ -84,4 +84,12 @@ Omit `reason` when `status` is `completed`. When `status` is `failed`, `fail` is
- Use required device farms; never substitute simulator-only testing.
- Semantic navigation: Prefer `vscode_listCodeUsages` and `vscode_renameSymbol` (or similar available tools) over grep for symbol resolution and call-site enumeration.
+## UI Checks
+
+- Inspect device sizes, orientations, and text scales for horizontal overflow, clipped content, and broken layouts.
+- Verify every interactive element has a real behavior or state toggle.
+- Verify every data-displaying UI has empty, loading, and error states.
+- Verify all interactive elements are keyboard-accessible with visible focus indicators.
+- Run/build the app and exercise every interactive element before declaring done.
+
diff --git a/agents/gem-orchestrator.agent.md b/agents/gem-orchestrator.agent.md
index 152bad9a1..8385cece2 100644
--- a/agents/gem-orchestrator.agent.md
+++ b/agents/gem-orchestrator.agent.md
@@ -35,13 +35,14 @@ MANDATORY: `Phase 0` is your non-delegable entry point for every single interact
- `research`: `research_question` and `expected_deliverable`.
- `execute`: `objective`, `acceptance_criteria`, and `constraints`.
- `debug`: `failure`, `expected_behavior`, and available `evidence`.
+- Intent priority: When multiple intents match, resolve by priority: `challenge` > `debug` > `research` > `execute` > `discuss`. The lowest-priority matching intent wins only when no higher-priority intent is clearly supported by the request's verbs, objects, and expected outcome.
- Read only relevant memory to request.
- Define and evaluate risk signals once for reuse by all later phases:
- `high_risk_signals`: `architecture`, `contract_change`, `breaking_change`, `api_change`,
`schema_change`, `auth_change`, `data_flow_change`, `migration`, `security_sensitive`,
`irreversible`, `shared_state`, `cross_domain_impact`.
- `critic_signals`: `architecture`, `breaking_change`, `cross_domain_impact`.
- - Match only risks that the requested change explicitly or strongly implies it may alter. A term mentioned as subject matter is not by itself a match.
+ - Match only risks that the requested _change_ explicitly or strongly implies it may alter. A term mentioned as subject matter or context is not by itself a match. Evaluate against what will be modified, not what the task is about.
- Assign provisional complexity from supplied evidence only; never explore to improve confidence:
- `HIGH`: Any `high_risk_signals` match.
- `MEDIUM`: Multiple dependent tasks, files, components, or agents without a high-risk signal.
@@ -64,7 +65,14 @@ MANDATORY: `Phase 0` is your non-delegable entry point for every single interact
#### Fast path: direct specialist execution
-For a single bounded task with clear acceptance criteria, one owner, and no high-risk signal:
+Eligibility requires all of:
+
+- Single owner: One narrowest specialist can complete the task end-to-end.
+- Bounded scope: The change is contained to one domain or file area.
+- Clear acceptance criteria: Explicitly supplied, or trivially inferable (e.g., "fix the typo" -> typo is corrected). If criteria require investigation to define, route to `gem-planner` first to define criteria, then fast-path execution.
+- No high-risk signal: No `high_risk_signals` match against the proposed change.
+
+When eligible:
- Use the assigned or generated `plan_id` for correlation only.
- Do not create a persistent plan.
@@ -72,14 +80,22 @@ For a single bounded task with clear acceptance criteria, one owner, and no high
- Delegate directly to the narrowest specialist.
- Require only relevant verification evidence.
-Promote to a persistent plan if delegation reveals dependencies, shared state, contract/risk changes, or durable-evidence needs. Keep `plan_id`, create `docs/plan/{plan_id}/plan.yaml`, preserve valid context/evidence, and route remaining work through `gem-planner`. Never redo non-stale completed work:
+#### Promotion: ephemeral to persistent plan
+
+`"Single owner"` means the initial specialist dispatch, not necessarily the final owner. Promotion during execution is expected, not exceptional. Promote when delegation reveals any of:
+
+- Multi-specialist dependency
+- Shared mutable state or cross-domain impact
+- Contract or API change
+- Durable evidence needs beyond a single specialist's scope
+
+On promotion:
-- preserve current state
-- preserve the current task owner; route only newly discovered scope to additional specialists
-- preserve the original task's current wave
-- keep completed work in its existing position and place dependent new tasks in later waves
-- create persistent plan
-- route remaining scope to planner
+- Keep `plan_id`, create `docs/plan/{plan_id}/plan.yaml`, preserve valid context/evidence.
+- Preserve current state and the current task owner; route only newly discovered scope to additional specialists.
+- Preserve the original task's current wave; completed work stays in place, dependent new tasks go in later waves.
+- Route remaining scope to `gem-planner`.
+- Never redo non-stale completed work.
### Phase 2: Planning
diff --git a/agents/gem-planner.agent.md b/agents/gem-planner.agent.md
index 5e04bb825..e3e58df95 100644
--- a/agents/gem-planner.agent.md
+++ b/agents/gem-planner.agent.md
@@ -165,6 +165,8 @@ tasks:
- Planning only: never implement code, edit unrelated files, or execute tasks.
- Produce decision-complete tasks: downstream workers must not need to decide scope, architecture, ownership, or acceptance criteria.
- Keep it simple: Apply YAGNI/KISS. Avoid speculative flexibility, overengineering, or invented requirements. Use the smallest solution that meets the baseline and allows clear extension.
+- Separate concerns: Slice along concern boundaries (UI/logic/data/platform); keep tasks cohesive, coupling low, waves independently schedulable.
+- Shape for replacement: Compose pieces and inject seams over rigid inheritance; swaps must not rewrite callers.
- Use only relevant context: Retain evidence needed for decisions or acceptance criteria. Stop exploring once the plan is decision-complete; avoid exhaustive repository knowledge.
- Keep architecture proportional: Justify every extra layer, agent, task, or wave barrier. Remove anything unnecessary to meet the baseline.
- Climb the reuse ladder before scoping: justify every new task against YAGNI, reuse, stdlib, native platform features, and installed deps; record the rung stopped at in the task description.
diff --git a/agents/gem-reviewer.agent.md b/agents/gem-reviewer.agent.md
index 3da4db9bd..c9cec3ffe 100644
--- a/agents/gem-reviewer.agent.md
+++ b/agents/gem-reviewer.agent.md
@@ -116,4 +116,11 @@ Omit `reason` when `status` is `completed`. `fail` is required when `status` is
- For `code`/`integration` targets, run an over-engineering pass: flag unrequested abstractions, avoidable new dependencies, boilerplate, diffs that could be shorter or more correct, and deliberate simplifications. Report each as a warning with the leaner alternative.
- Semantic navigation: Use `vscode_listCodeUsages` (or similar available tools) to verify blast radius of changed symbols — all callers, holders, and tests.
+## Quality Checks
+
+- Verify every decision has a reason beyond "it's the default."
+- Require a one-line reason for all major decisions.
+- Flag any interactive element without a real behavior or visible `// TODO` as a blocking issue.
+- Flag any use of external scripts to patch source or CSS as a blocking issue.
+
diff --git a/docs/README.agents.md b/docs/README.agents.md
index eac43b3ef..608834918 100644
--- a/docs/README.agents.md
+++ b/docs/README.agents.md
@@ -90,7 +90,7 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-agents) for guidelines on how to
| [Doublecheck](../agents/doublecheck.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fdoublecheck.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fdoublecheck.agent.md) | Interactive verification agent for AI-generated output. Runs a three-layer pipeline (self-audit, source verification, adversarial review) and produces structured reports with source links for human review. | |
| [Droid](../agents/droid.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fdroid.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fdroid.agent.md) | Provides installation guidance, usage examples, and automation patterns for the Droid CLI, with emphasis on droid exec for CI/CD and non-interactive automation | |
| [Drupal Expert](../agents/drupal-expert.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fdrupal-expert.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fdrupal-expert.agent.md) | Expert assistant for Drupal development, architecture, and best practices using PHP 8.3+ and modern Drupal patterns | |
-| [Dynatrace Expert](../agents/dynatrace-expert.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fdynatrace-expert.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fdynatrace-expert.agent.md) | The Dynatrace Expert Agent integrates observability and security capabilities directly into GitHub workflows, enabling development teams to investigate incidents, validate deployments, triage errors, detect performance regressions, validate releases, and manage security vulnerabilities by autonomously analysing traces, logs, and Dynatrace findings. This enables targeted and precise remediation of identified issues directly within the repository. | [dynatrace](https://github.com/mcp/io.github.dynatrace-oss/Dynatrace-mcp)
[](https://aka.ms/awesome-copilot/install/mcp-vscode?name=dynatrace&config=%7B%22url%22%3A%22https%3A%2F%2Fpia1134d.dev.apps.dynatracelabs.com%2Fplatform-reserved%2Fmcp-gateway%2Fv0.1%2Fservers%2Fdynatrace-mcp%2Fmcp%22%2C%22headers%22%3A%7B%22Authorization%22%3A%22Bearer%20%24COPILOT_MCP_DT_API_TOKEN%22%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-vscodeinsiders?name=dynatrace&config=%7B%22url%22%3A%22https%3A%2F%2Fpia1134d.dev.apps.dynatracelabs.com%2Fplatform-reserved%2Fmcp-gateway%2Fv0.1%2Fservers%2Fdynatrace-mcp%2Fmcp%22%2C%22headers%22%3A%7B%22Authorization%22%3A%22Bearer%20%24COPILOT_MCP_DT_API_TOKEN%22%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-visualstudio/mcp-install?%7B%22url%22%3A%22https%3A%2F%2Fpia1134d.dev.apps.dynatracelabs.com%2Fplatform-reserved%2Fmcp-gateway%2Fv0.1%2Fservers%2Fdynatrace-mcp%2Fmcp%22%2C%22headers%22%3A%7B%22Authorization%22%3A%22Bearer%20%24COPILOT_MCP_DT_API_TOKEN%22%7D%7D) |
+| [Dynatrace Expert](../agents/dynatrace-expert.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fdynatrace-expert.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fdynatrace-expert.agent.md) | The Dynatrace Expert Agent integrates observability and security capabilities directly into GitHub workflows, enabling development teams to investigate incidents, validate deployments, triage errors, detect performance regressions, validate releases, and manage security vulnerabilities by autonomously analysing traces, logs, and Dynatrace findings. This enables targeted and precise remediation of identified issues directly within the repository. | [dynatrace](https://github.com/mcp/io.github.Dynatrace/dynatrace-for-ai)
[](https://aka.ms/awesome-copilot/install/mcp-vscode?name=dynatrace&config=%7B%22url%22%3A%22https%3A%2F%2Fpia1134d.dev.apps.dynatracelabs.com%2Fplatform-reserved%2Fmcp-gateway%2Fv0.1%2Fservers%2Fdynatrace-mcp%2Fmcp%22%2C%22headers%22%3A%7B%22Authorization%22%3A%22Bearer%20%24COPILOT_MCP_DT_API_TOKEN%22%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-vscodeinsiders?name=dynatrace&config=%7B%22url%22%3A%22https%3A%2F%2Fpia1134d.dev.apps.dynatracelabs.com%2Fplatform-reserved%2Fmcp-gateway%2Fv0.1%2Fservers%2Fdynatrace-mcp%2Fmcp%22%2C%22headers%22%3A%7B%22Authorization%22%3A%22Bearer%20%24COPILOT_MCP_DT_API_TOKEN%22%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-visualstudio/mcp-install?%7B%22url%22%3A%22https%3A%2F%2Fpia1134d.dev.apps.dynatracelabs.com%2Fplatform-reserved%2Fmcp-gateway%2Fv0.1%2Fservers%2Fdynatrace-mcp%2Fmcp%22%2C%22headers%22%3A%7B%22Authorization%22%3A%22Bearer%20%24COPILOT_MCP_DT_API_TOKEN%22%7D%7D) |
| [Elasticsearch Agent](../agents/elasticsearch-observability.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Felasticsearch-observability.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Felasticsearch-observability.agent.md) | Our expert AI assistant for debugging code (O11y), optimizing vector search (RAG), and remediating security threats using live Elastic data. | elastic-mcp
[](https://aka.ms/awesome-copilot/install/mcp-vscode?name=elastic-mcp&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22mcp-remote%22%2C%22https%253A%252F%252F%257BKIBANA_URL%257D%252Fapi%252Fagent_builder%252Fmcp%22%2C%22--header%22%2C%22Authorization%253A%2524%257BAUTH_HEADER%257D%22%5D%2C%22env%22%3A%7B%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-vscodeinsiders?name=elastic-mcp&config=%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22mcp-remote%22%2C%22https%253A%252F%252F%257BKIBANA_URL%257D%252Fapi%252Fagent_builder%252Fmcp%22%2C%22--header%22%2C%22Authorization%253A%2524%257BAUTH_HEADER%257D%22%5D%2C%22env%22%3A%7B%7D%7D)
[](https://aka.ms/awesome-copilot/install/mcp-visualstudio/mcp-install?%7B%22command%22%3A%22npx%22%2C%22args%22%3A%5B%22mcp-remote%22%2C%22https%253A%252F%252F%257BKIBANA_URL%257D%252Fapi%252Fagent_builder%252Fmcp%22%2C%22--header%22%2C%22Authorization%253A%2524%257BAUTH_HEADER%257D%22%5D%2C%22env%22%3A%7B%7D%7D) |
| [Electron Code Review Mode Instructions](../agents/electron-angular-native.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Felectron-angular-native.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Felectron-angular-native.agent.md) | Code Review Mode tailored for Electron app with Node.js backend (main), Angular frontend (render), and native integration layer (e.g., AppleScript, shell, or native tooling). Services in other repos are not reviewed here. | |
| [Ember](../agents/ember.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fember.agent.md)
[](https://aka.ms/awesome-copilot/install/agent?url=vscode-insiders%3Achat-agent%2Finstall%3Furl%3Dhttps%3A%2F%2Fraw.githubusercontent.com%2Fgithub%2Fawesome-copilot%2Fmain%2Fagents%2Fember.agent.md) | An AI partner, not an assistant. Ember carries fire from person to person — helping humans discover that AI partnership isn't something you learn, it's something you find. | |
diff --git a/plugins/gem-team/README.md b/plugins/gem-team/README.md
index beb65092f..78e498962 100644
--- a/plugins/gem-team/README.md
+++ b/plugins/gem-team/README.md
@@ -139,6 +139,7 @@ Gem Team uses a structured workflow to turn AI coding into a reliable engineerin
- **Cost Efficiency**: Model routing, output hygiene, and compact handoffs ensure you only use the tokens you need. Evidence travels by reference, not by copy — keeping context usage low and cache hits high across waves.
- **Failure Classification**: Every failure is classified (retry, fixable, replan, flaky, regression, platform-specific, test-bug) so the Orchestrator routes it to the right agent instead of blindly retrying.
- **Verification Boundary**: The Orchestrator never re-verifies or second-guesses specialist output. Verification is owned exclusively by the specialist responsible for the work.
+- **Quality Directives**: Every agent follows specific rules that prevent common AI coding issues: no dead buttons, no buzzwords, no template filler, and every decision has a reason.
## How it Works
@@ -150,20 +151,20 @@ Gem Team installs a set of specialized agents that work together under the guida
### Agent Roles
-| Role | Description |
-| :------------------ | :------------------------------------------------------------------------------------------------------------------ |
-| **Orchestrator** | Classifies intent, routes work, tracks state, and enforces verification gates. Never re-verifies specialist output. |
-| **Planner** | Creates bounded wave plans with YAGNI/KISS scope reduction: milestones, routing, handoffs, risks, and criteria. |
-| **Implementer** | Implements features, fixes, and refactors with TDD. Covers happy paths, boundaries, errors, and state transitions. |
-| **Reviewer** | Independent reviews for quality, security, and compliance. Read-only critic mode for decisions. |
-| **Debugger** | Root-cause analysis, stack traces, regression bisection. Adds a reproduction test; never implements fixes. |
-| **Researcher** | Codebase exploration in five budgeted modes: scan, question, audit, trace, deep. |
-| **Browser Tester** | E2E browser tests with visual, accessibility, performance, network, and regression checks. |
-| **Mobile Tester** | Mobile E2E on iOS/Android with Detox, Maestro, or Appium. |
-| **DevOps** | Infrastructure, CI/CD, containers, health checks, rollback, and production approvals. |
-| **Documentation** | Technical docs, READMEs, API references, diagrams, and walkthroughs. |
-| **Code Simplifier** | Removes dead code, reduces complexity, consolidates duplicates, and improves naming. |
-| **Skill Creator** | Extracts high-confidence patterns into reusable `SKILL.md` files and assets. |
+| Role | Description |
+| :------------------ | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Orchestrator** | Classifies intent, routes work, tracks state, and enforces verification gates. Never re-verifies specialist output. |
+| **Planner** | Creates bounded wave plans with YAGNI/KISS scope reduction and concern-separated slices: milestones, routing, handoffs, risks, and criteria. |
+| **Implementer** | Implements features, fixes, and refactors with TDD. Covers happy paths, boundaries, errors, and state transitions. Applies SOLID, fail-fast, and least-surprise. Every major decision has a one-line reason. No dead buttons. |
+| **Reviewer** | Independent reviews for quality, security, and compliance. Read-only critic mode for decisions. Verifies every decision has a reason. Flags dead buttons and external script patches as blocking issues. |
+| **Debugger** | Root-cause analysis, stack traces, regression bisection. Adds a reproduction test; never implements fixes. |
+| **Researcher** | Codebase exploration in five budgeted modes: scan, question, audit, trace, deep. |
+| **Browser Tester** | E2E browser tests with visual, accessibility, performance, network, and regression checks. |
+| **Mobile Tester** | Mobile E2E on iOS/Android with Detox, Maestro, or Appium. |
+| **DevOps** | Infrastructure, CI/CD, containers, health checks, rollback, and production approvals. |
+| **Documentation** | Technical docs, READMEs, API references, diagrams, and walkthroughs. No buzzwords. Every section exists because the product needs it. No fabricated statistics. |
+| **Code Simplifier** | Removes dead code, reduces complexity, consolidates duplicates, and improves naming. Every refactoring has a one-line reason. No buzzwords. Removes AI-slop comments. |
+| **Skill Creator** | Extracts high-confidence patterns into reusable `SKILL.md` files and assets. |
## Compatible Tools
diff --git a/plugins/gem-team/plugin.json b/plugins/gem-team/plugin.json
index a9c7fb8f2..dc15d3387 100644
--- a/plugins/gem-team/plugin.json
+++ b/plugins/gem-team/plugin.json
@@ -44,5 +44,5 @@
"license": "Apache-2.0",
"name": "gem-team",
"repository": "https://github.com/mubaidr/gem-team",
- "version": "1.119.0"
+ "version": "1.121.0"
}