Use it before building a Salesforce automation or schema change, including when you need to compare approaches, update or delete a named element, or understand the effects of a proposed change.

Before offering approaches, including for requests without a named change set, it checks for automation that matches the requested purpose and writes the relevant field or creates the requested record. When it finds a confirmed match, that option leads as 'Use what you already have'. Apex classes with an unknown active status remain candidates unless an inactive or deleted fact excludes them.

For named automation updates, it compares current and proposed entry conditions when the conditions change. Its order-of-execution screen combines those comparisons with the existing field screen to show pre-existing conflicts.

It checks whether existing automation already does the requested work, traces incoming references and outgoing connections, reviews save-driven effects, and identifies dependencies, migration needs and order-of-execution concerns.

For automation deletes, it checks which jobs would be lost or partly covered and asks whether to delete anyway or move the uncovered work first.

A blocking finding leads the report and holds the backlog as not drafted. You can change the request, choose another approach when options were offered, or ask the playbook to plan the confirmed change anyway. That reply triggers a fresh impact trace, and the resulting draft carries the blocking findings as flags with your reply verbatim on the change story.

This is analysis and planning only. You make every change. The playbook does not change Salesforce metadata or save Elements stories.

Field population is reported as a percentage only.

Install and connect the core elements plugin to the Elements MCP server. MCP must be enabled for the Elements Space. See Connect your AI assistant to the Elements MCP server for core setup.

Automation summaries require Automation & Execution Intelligence (an add-on on Core Metadata Management; included in Advanced Metadata Management). Summaries must already exist for an automation in the target org. The playbook checks this first and stops before confirming or tracing the change until the summaries are available. Wait for summaries to finish, then say 'retry'.

Use an Elements model for the Salesforce org. A model with an earlier completed sync can be analyzed even when its latest sync failed; the report gives the date of the completed sync and says the latest sync failed. If the model has never completed a sync, wait for one and retry.

Python 3 must run where the playbook scripts run.

"Assess the impact of adding values to Opportunity.Lost_Reason__c."

"Compare approaches for adding an approval step to Opportunity."

"Resume my change-impact assessment."

A sentence describing the proposed automation or schema change, including the object and named element when known.

The Elements Space and org model to use when more than one is available. With one suitable model, the playbook selects it and tells you.

Answers to any confirmation or approach question. For an automation delete, the playbook may ask whether to delete despite lost work or move uncovered work first.

A self-contained HyperText Markup Language (HTML) impact report, impact-report.html, with a JavaScript Object Notation (JSON) report record, impact-report.json.

A draft Markdown backlog, backlog.md, and its JSON record, backlog.json, with proposed work, acceptance criteria, delivery order and any flags. Story member files accompany grouped work where needed.

The report describes the confirmed request, selected org model and sync date, alternatives and choices, affected components, evidence gaps, data and automation effects, migration needs, findings and proposed delivery work.

Incoming references and outgoing connections are shown separately. A direction that was not read is marked 'not assessed'. A completed read with no results is reported as zero.

The backlog is a draft and has not been saved as Elements stories. If a blocking finding is unresolved, both backlog files say that the backlog was not drafted and include the finding.

A model whose latest sync failed is identified in the report, which says that the analysis uses its last complete sync.

get_space_context and list_reference_models: identify the available Elements Space and org models.

search_metadata, get_metadata_component, get_metadata_source and list_metadata_by_criteria: resolve targets and read model details, definitions, fields and values.

get_dependencies: read component relationships and dependency evidence.

explain_metadata_components: check automation summaries and provide automation evidence.

run_code_search: search for possible source references outside available Apex bodies.

run_data_load_impact: assess save-driven effects of a change.

The engagement directory stores execution-state.json, report and backlog files, and intermediate evidence used by the analysis.

The work/ folder stores downloaded evidence bundles and normalized files used to produce the report and backlog.

The report and backlog may contain org object, field, automation and component names; descriptions and automation summaries; dependency and source-reference evidence; population percentages; findings; and your request and replies.

The playbook does not change Salesforce metadata or save Elements stories. Review report, backlog and member files before sharing them, because they contain information from your org and conversation.

Codex: command-line interface (CLI).

Other tools are untested.