Summary

Sam asked that if parallel work, subagents, skills, Superpowers, or other knowledge/tools would benefit the agent receiving the handoff, that guidance should be included. I updated the RingCentral/SMS Magic handoffs accordingly.

What Was Updated

• admin/handoffs/HANDOFF-sms-magic-retirement-ringcentral-v2-2026-05-12.md now has a Recommended Agent Strategy section.
• admin/handoffs/HANDOFF-ringcentral-matter-tab-important-details-2026-05-01.md now has a Recommended Agent Strategy section under implementation phases.
• admin/_qa-queue/2026-05-12.md now notes the handoff enhancement.

Guidance Added

Recommended skills/tooling now include:

• litify-live-defaults before Salesforce/Litify work.
• superpowers:dispatching-parallel-agents for independent read-only discovery lanes.
• superpowers:subagent-driven-development once there is a concrete implementation plan.
• superpowers:verification-before-completion before claiming the RingCentral tab, chat timeline, or SMS Magic retirement is done.
• Browser/Chrome or frontend testing/debugging skills for iframe, CSP, console, and visual QA.
• Notion export tooling at closeout.

Recommended subagent lanes now include:

• Live metadata inventory, read-only.
• RingCentral data-source validation, read-only.
• SMS Magic archive/history mapping, read-only.
• RingCentral V2 Apex/LWC implementation, write-scoped.
• Salesforce metadata placement, write-scoped.