Check and configure documentation capabilities before an OEM/ISV Advisor interaction. Use when the advisor starts, when Salesforce Docs MCP or official-documentation access may be missing, when a customer asks to install or approve documentation tools, or…
Use for Data 360 architecture, data-kit workflow, scratch entitlement, metadata packageability, activation ordering, and partner-solution integration decisions. Owns Data 360 architecture and implementation patterns that affect partner solutions and packaging.
Route and synthesize decisions about PBO Dev Hubs, namespaces, scratch org shape, persistent development orgs, demos, trials, provisioning, developer access, and environment lifecycle. Use when a partner asks which Salesforce org or environment should perform…
Use when choosing scratch, PDE, Test/Demo, Trialforce Source, template-backed, customer-trial, sandbox, or other partner environments for a lifecycle job. Owns Choosing scratch, PDE, test/demo, Trialforce source, template, customer trial, and other partner…
Advise Salesforce partners on Headless Toolkit and MCP client/server choices, managed-package boundaries, HXL output, and delivery to Agentforce, Slackbot, Claude, or ChatGPT. Use for architecture decisions or Salesforce DX assessments; route builds to global…
Route and synthesize implementation decisions for Agentforce, Data 360, Slack, Tableau Next, Apex, APIs, prompts, MCP, sub-agents, state, long-running actions, testing, and user experience. Use after product and environment decisions are known and a partner…
Use after product and environment decisions to route implementation questions across Agentforce, Data 360, Slack, Tableau Next, Apex, APIs, prompts, MCP, and dynamically discovered Salesforce skill libraries. Owns Routes product-specific implementation…
Use before creating a managed 2GP package or when validating PBO ownership, package identity, namespace, source path, and irreversible foundation decisions. Owns PBO ownership, package identity, namespace, project blueprint, and irreversible creation gates.
Main entrance for Salesforce OEM and ISV partner advisory work across solution discovery, packaging, development environments, implementation, platform constraints, security readiness, and operations. Use when a partner asks for guidance and the correct…
Guide testing strategy, CI/CD, release cadence, versioning, upgrades, rollback, monitoring, regulated delivery, incident response, and lifecycle operations for OEM or ISV products. Use when a partner needs to prove a release is reliable or operate it safely…
Use for package version numbering, NEXT builds, linear ancestry, explicit dependencies, transitive dependency settings, patches, and upgrade-path diagnosis. Owns Version numbering, linear ancestry, dependencies, patches, upgrade paths, and related failure…
Use for managed 1GP-to-2GP migration or recovery from a managed 2GP package created under the wrong Dev Hub. Owns Managed 1GP-to-2GP migration and wrong-Dev-Hub transfer decision trees, eligibility, preservation, and recovery.
Use when deciding whether an exact managed package version is ready to promote, release, recommend, list, or distribute. Owns Promotion readiness, irreversible release gate, recommended version, and evidence required before release.
Use when a partner wants a read-only repository assessment for packageable metadata, source boundaries, dependencies, unsupported components, or remediation evidence. Owns Repository and metadata packageability inspection, unsupported components, boundaries,…
Route and synthesize OEM or ISV decisions about packageability, managed 2GP, package architecture, versions, ancestry, promotion, migration, listings, distribution, and upgrades. Use when a partner asks whether or how a Salesforce solution should be packaged…
Use when a partner asks whether to package, which packaging model to use, where package boundaries belong, or how packaging affects distribution and upgrades. Owns Whether, what, and how to package; managed 2GP, migration, package boundaries, and distribution…
Use when identifying a Partner Business Org, selecting the ISV Dev Hub, checking lifecycle status and entitlements, or recovering from an incorrect Dev Hub foundation. Owns PBO identification, activation, Dev Hub and managed 2GP baseline, entitlement…
Identify Salesforce runtime, metadata, packaging, file, scale, timeout, performance, volume, immutability, and capability constraints. Use when a design might depend on a current platform limit, unsupported pattern, guardrail, or workaround.
Use when designing or assessing project-scratch-def.json, editions, features, settings, object settings, product entitlements, or package-build shape. Owns Scratch definition as code, editions, features, settings, product entitlement checks, and package-build…
Assess secure architecture, data protection, AgentExchange or AppExchange Security Review preparation, testing and scanner evidence, submission materials, and remediation readiness. Use when an OEM or ISV solution must identify security risk or prepare…
Validate an OEM or ISV product idea, target user, Salesforce fit, product boundary, business outcome, and candidate solution direction. Use when a partner is still deciding what to build, whether Salesforce is the right platform, or which advisor capability…
Use for Tableau Next scratch enablement, Data 360 dependencies, semantic models, workspaces, visualizations, dashboards, deployment ordering, and integration decisions. Owns Tableau Next implementation and integration decisions relevant to partner solutions.