sf-demo-scout

Orchestrator for SF Demo Prep deployment. Parses a completed spec from /scout-sparring, delegates deployment to Sonnet sub-agents in phases, and writes a consolidated change log. Activate with /scout-building.

One-stop install, refresh, and repair for Scout. Run on first install, after a Scout update, or whenever something feels broken. Idempotent — safe to re-run any time.

Opus sparring partner for Salesforce demo preparation. Handles both new scenario discovery and targeted iterations on existing demos. Produces a structured spec for /scout-building to deploy. Activate with /scout-sparring.

Switch to a different Salesforce demo org.

Salesforce debug log analysis and troubleshooting with 100-point scoring. TRIGGER when: user analyzes debug logs, hits governor limits, reads stack traces, or touches .log files from Salesforce orgs. DO NOT TRIGGER when: running Apex tests (use running-apex-tests), generating or fixing Apex code (use generating-apex), or Agentforce session tracing (use observing-agentforce).

Canonical deployment rules for Flows, Apex, LWC, Agentforce, Page Layouts, Queues, and Picklists in SF Demo Prep. Pattern-gated 3-attempt rule, known deploy-error patterns, rollback commands, and per-category deployment procedures. TRIGGER when: a phase sub-agent needs deployment rules outside its inlined scope, or needs to verify rollback command syntax. DO NOT TRIGGER when: deploying metadata (phase prompts inline the relevant rules), during sparring, or for permission set generation.

Decision tree for when to consult the Salesforce Docs MCP — YES/NO rules, citation format, and degraded-mode handling. TRIGGER when: deciding whether to call salesforce_docs_search/fetch (sparring Stage 4, building error recovery, sub-agent unfamiliar-error path). DO NOT TRIGGER when: actually executing a docs search (the decision is already made), during audits, or for standard metadata generation.

Format and procedure for auditing a Salesforce demo org — required content, priority flags, and ProfileLayout query patterns. TRIGGER when: audit sub-agents need the canonical output format, section structure, or ★ priority flag rules. DO NOT TRIGGER when: running the audit (sub-agent prompts have inlined procedures), generating specs, or deploying metadata.

Salesforce DevOps automation using sf CLI v2. TRIGGER when: user deploys metadata, creates/manages scratch orgs or sandboxes, sets up CI/CD pipelines, or troubleshoots deployment errors with sf project deploy. DO NOT TRIGGER when: writing Apex code (use generating-apex), building LWC components (use generating-lwc-components), creating metadata definitions (use generating-custom-object or generating-custom-field), or querying org data (use handling-sf-data).

1 hook across 1 event