What problem does it solve? Understanding what an Agentforce agent actually does requires manually tracing planners, topics, actions, flows, Apex classes, and prompt templates across multiple Salesforce metadata types. This Skill automates that discovery, producing a normalized metadata tree and a human-readable architecture document in under a minute. ## Core Features & Use Cases - Declared architecture snapshot: Resolves a BotDefinition and BotVersion, then fans out parallel Tooling SOQL queries to map the planner, topics, actions, flows, Apex, prompt templates, and NGA plugins into a single normalized JSON tree. - Rendered documentation: Produces an architecture.md file with an action tree, topic anatomy, action catalog, data-flow diagram, and Mermaid invocation graphs, plus a dependency graph when unresolved references or cycles exist. - Classic ReAct and NGA support: Normalizes both planner families into one tree shape, routing NGA InvocationTargets by Salesforce ID prefix and surfacing unresolved references explicitly instead of dropping them. - Use Case: Ask to document the architecture of MyAgent in your org, and receive a metadata tree JSON plus a sectioned architecture document with Mermaid diagrams, cached for fast re-runs and diffable across versions (e.g. v3 vs v5). ## Quick Start Ask the assistant to document the architecture of your agent by providing the agent API name and your sf CLI org alias, for example: document the architecture of MyAgent in my-org-alias.
