Skip to content

forcedotcom/sf-skills / plugins/builder/agentforce-adlc/skills/agentforce-bot-upgrade

agentforce-bot-upgrade

Flagged

Use this skill to upgrade Einstein Bots into Agentforce agents end-to-end in a single pass, orchestrating per-bot Agent Spec generation, agentforce-generate authoring, and post-conversion .agent enhancements. TRIGGER when: user asks to migrate, upgrade, or convert one or more Einstein Bots (BotDefinition/BotVersion chatbots) to Agentforce agents; runs a multi-bot bot-to-agent upgrade; needs Einstein Bot metadata turned into Agent Spec handoffs and generated .agent agents; convert bots to agents; upgrade my service bots; move bots to Agentforce. DO NOT TRIGGER when: user already has an approved Agent Spec and only wants direct .agent authoring, deploy, test, or observe flows; user wants to migrate or upgrade an EXISTING Agentforce agent from a legacy GenAiPlannerBundle to an NGA aiAuthoringBundle (that is agentforce-generate's 'Migrate a Legacy Agent to Agent Script' flow, not an Einstein Bot upgrade); the request is unrelated to Einstein Bot migration.

references/quality-checklist.md

View on GitHub
# Quality Checklist

Run this checklist before handing off to `/agentforce-generate`.

## Completeness

- Input mode is explicitly recorded for the run (Online org-backed or Offline local metadata).
- Agent Spec uses the exact section names/order from [agent-spec-template.md](../assets/_vendored/agent-spec-template.md) (from the `agentforce-generate` skill).
- Every major bot capability is represented in the Agent Spec.
- Every critical dialog/intent/action is either mapped or listed in `unmapped_items`.
- Fallback and escalation behavior is explicit.
- The Agent Spec includes the default `ambiguous` (unclear requests) and `off_topic` (out-of-scope requests) subagents, each with its own router transition.

## Fidelity

- Action purpose and I/O are preserved from source metadata where available.
- For Offline mode, action signatures come from local Apex/Flow/referenced files when present, falling back to bot metadata mappings when they are not; unresolved signature details are tracked in `open_questions` (non-blocking).
- Dialog-to-subagent and intent-to-subagent mappings are consistent.
- High-risk flows contain clear deterministic guidance.

## Handoff Readiness

- Agent Spec markdown is coherent and structured for implementation.
- Handoff JSON is machine-readable and aligned with markdown.
- Open questions are specific, non-duplicative, and decision-ready.
- Open questions are resolved — one-by-one with the user in interactive mode, or auto-applied from recommended defaults when `--interactive=false` — and each resolution is reflected in both Agent Spec and `extraction-summary.json`.

## Failure Conditions (must fix before handoff)

- Missing action inventory for flows that clearly invoke actions
- Claimed parity while unresolved items are not documented
- Ambiguous routing with no fallback
- Unresolved or ambiguous open questions remain before automatic handoff to `/agentforce-generate`
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall