Scopes Shipped
A scope is a deterministic pre-filter defined as team data: which specialists convene, and which of their specialties run under it.
Nineteen scopes ship today. risk is the default — it asks "is there a bug or a design decision here that bites later?" Its roster is the union of the eight focused defect scopes, which is thirteen specialists, plus one always-on fourteenth: the test-coverage reviewer, narrowed under this scope to the single question of whether new risk-bearing code is covered at all. The concern scopes are deliberately opt-in and excluded, because a default review that also grades you on internationalization drowns the defects in backfill work.
The nineteen
| Scope | In risk? | Covers |
|---|---|---|
| risk | default | Correctness and design defects in the code as written |
| security | yes | Auth, authz, input validation, secrets, transport, CSP/CORS, dependencies |
| safety | yes | Privacy, sensitive data, user safety, LLM red-teaming |
| data | yes | Schema, keys, indexing, constraints, transactions, sync |
| api | yes | Contracts, error responses, pagination, rate limiting, real-time |
| reliability | yes | Fail-fast, idempotency, retries, timeouts, offline, immutability |
| architecture | yes | Boundaries, decomposition, DI, concurrency, optimize-for-change |
| code-quality | yes | Simplicity, YAGNI, design-for-deletion, hygiene, naming |
| performance | yes | Caching, algorithmic complexity, query and index optimization |
| conformance | no | Adjudicate against an acceptance contract, per criterion |
| completeness | opt-in | What should be present but isn't — a11y, i18n, tests |
| testing | partial | Test pyramid, property and mutation tests, flakiness, doubles |
| accessibility | opt-in | Semantic roles, dynamic type, contrast, platform a11y APIs |
| i18n | opt-in | Localization, RTL, font scaling |
| ui-ux | opt-in | Layout, typography, spacing, forms, feedback, motion |
| observability | opt-in | Logging, analytics, debug mode, feature flags |
| platform-native | opt-in | Native controls, notifications, widgets, deep links, handoff |
| claude-code | signal | Claude Code agents, skills and rules |
| recipe | signal | Cookbook recipes — template conformance, source fidelity |
It is a pre-filter, not a suggestion
The scope resolves before anything agentic runs. A scope block in the team definition names which specialists convene; a line in each specialist narrows which of its own specialties fire under that scope. Two scopes on one command line union rather than intersect, so --security --data is "everything either one would have convened."
The live list
Every scope, with the exact specialists it convenes, is under Teams → devteam → Scopes — generated from the team data rather than typed here, so it cannot drift.