Specialists give you focused judgment on demand. Brief them like a capable colleague you just met: name the sources, state the constraints, define what done looks like, then check the work before it becomes workspace truth.

​
Pick the right kind

  • Built-in specialists (Bright, Advisor, Assistant, Designer, Engineer, Explorer, Product Manager, Product Researcher, Researcher) cover common roles. Use one for a quick point of view or bounded support. The roster and what each one owns is in Agents.
  • Custom agents are roles you define with stable instructions, decision boundaries, and escalation rules. Create them on Capabilities → Agents; see Build skills and named agents.
Type @ in the composer to mention either kind in a session.

​
The grounding contract

Give a specialist room to think and no room to invent:
  • Name the authoritative sources.
  • Forbid facts that are not present in those sources.
  • Require observed facts, inferences, proposals, and unknowns to be separated.
  • Request citations to issue fields, document sections, or connected records.
  • Set a tool budget and a stop condition.
  • Keep writes off until a human accepts the analysis.
Neither kind removes approvals: tool use still follows your mode and the approval prompts in chat (see Context, permissions, and safe operation).

​
Review before promotion

Before you copy a specialist’s response into a plan, issue, or document, verify every proper noun, URL, ticket identifier, dependency, metric, and technical component. Those details are where unsupported invention costs the most.