Revops

Salesforce data operations (Brite edition) with 130-point scoring. TRIGGER when user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, works in brite-salesforce, asks about HubSpot migration ETL, email-as-Task migration semantics, setSaveAsActivity Email Logs monitoring, Bulk API session-permset gotchas, CreateAuditFields INSERT-only behavior,

Creates and validates Salesforce Flows (Brite edition) with 110-point scoring. TRIGGER when user builds or edits record-triggered, screen, autolaunched, or scheduled flows, touches .flow-meta.xml files, works in brite-salesforce, asks about the Apex-first flow policy (Flows only for screen flows + simple notifications), the Screen-Flow-deploy-as-Draft trap (regardless of source `<status>Active</status>`), `sf data update record` failing to activate flows, post-deploy Tooling API verification (`SELECT Status FROM Flow WHERE Definition.DeveloperName = '...'`), scratch-org flow activation gaps, or `/revops:post-deploy-runbook` Phase 2 cross-reference. DO NOT TRIGGER when Apex automation (use sf-apex), process builder migration questions only, or non-Flow declarative config (use sf-metadata).

Apex test execution and coverage discipline (Brite edition) with 120-point scoring. TRIGGER when user runs Apex tests, checks coverage, fixes failing tests, touches *Test.cls / *_Test.cls files, works in brite-salesforce, asks about 100% class coverage targets, @TestSetup static-state trap, Queueables inside Test.stopTest() re-entering handlers, @TestVisible + Test.isRunningTest() escape-hatch gating, Bypass_Validation_Rules honoring in tests, LWC Jest pre-commit, or scratch-org-per-PR validation. DO NOT TRIGGER when writing Apex production code (use sf-apex), Agentforce agent testing (use sf-ai-agentforce-testing), or Jest/LWC tests (use sf-lwc).

Salesforce Permission Set / Permission Set Group analysis and access auditing for Brite's brite-salesforce repo. TRIGGER when user asks "who has access to X?", analyzes permsets or permset groups, adds CustomField FLS (7-permset sync reminder), touches Base_CRM_Access or {Team}_Group / {Team}_Management_Group naming, debugs Lifecycle_Stage__c automation-only restrictions, session-based permset activation (HubSpot_Migration, SessionPermissionSetActivation), CreateAuditFields INSERT-only gotcha, or restricted record-type visibility scoping (Acquisition, Partner_Fulfillment). DO NOT TRIGGER when creating new metadata (use sf-metadata), deploying permission sets (use sf-deploy), or Apex-managed sharing logic (use sf-apex).