Elements Map and Design is a guided playbook for mapping and designing Salesforce business architecture in Elements. Describe what you need through the /start skill, and it routes the request to the right map or design workflow.
Elements Map and Design is an Elements MCP playbook. See What is an MCP playbook? to learn how playbooks work.
What it does and when to use it
Create process maps, customer journeys, data models, interaction flows, capability maps and system architecture from supported inputs such as a description, transcript, standard operating procedure (SOP), document or picture. It can also map processes from vendor documentation or show an agent package as a process.
Read the connected org to map the business process behind an object's data model, explain one automation, trace an automation chain, or show the automations behind each status in an org-based process map.
Derive a solution design from an Elements process map, map the org's integration landscape, or check how far the org implements a design. The implementation check reports gaps and can colour the map by result; ask to reset the colours to remove them.
Data models and system architecture diagrams can be amended. Other diagram types are drawn new.
Requirements
Install and connect the core
elementsplugin to the Elements MCP server. See Connect your AI assistant to the Elements MCP server for core setup.Python 3.8 or later and an assistant host that can run local scripts.
The process-map design and org-integration workflows also need
curl. The process-map design workflow needs thepython-docxpackage to create its Word document; LibreOffice and Pillow are optional for adding diagram pictures to that document.
Install
Claude Code
Claude Code
/plugin marketplace add Q9Elements/elements-mcp-server
/plugin install elements-map-and-design@elements
Codex
Codex
codex plugin marketplace add Q9Elements/elements-mcp-server
codex plugin add elements-map-and-design@elements
How it runs
Start with
/start(or/elements-map-and-design:start) and describe the map, source and goal.The front door routes the request to a reader, a design workflow or a new-map workflow. It can resume supported work from its saved run folder.
The workflow reads the supplied material or connected org, checks the map model, and draws or amends the diagram in Elements. Design and org-integration workflows pause at review points before drawing.
For an implementation check, review the findings and choose whether to colour the map. Ask to reset the colours to remove them.
What you get
Draft diagrams in Elements, including process maps, customer journeys, data models, interaction flows, capability maps and system architecture.
Depending on the request, a solution overview document and data access matrix, an integration report, automation explanations, or an implementation gap report.
Some runs add names to the Elements Space's resource library so they can appear on diagram cards.
What stays with you
Diagrams are created as drafts in Elements. You decide when to release them.
Nothing in Salesforce changes.
Elements tools used
The plugin calls these Elements tools: create_map, describe_metadata_schema, explain_metadata_components, get_access, get_analysis_result, get_component_change_history, get_component_usage, get_dependencies, get_diagram, get_metadata_component, get_metadata_source, get_org_health_detail, get_process_map, get_process_map_outline, get_space_context, list_managed_packages, list_metadata_by_criteria, list_process_maps, list_reference_models, manage_diagram, run_automation_inventory, run_code_search, search_metadata and understand_org_health.
Tested with
Claude: command-line interface (CLI).
Version
Version 1.0.0.