Session Objective
Sam asked whether the long opportunities backlog should be worked newest-to-oldest and whether subagents could divide and conquer it.
What Was Done
- Used the
superpowers:subagent-driven-development frame for read-only triage.
- Spawned three explorer subagents against
/Users/samaguiar/Documents/Projects/admin/opportunities-and-expansion-log.md.
- Split review by date band: late May, mid-to-late April, and older April.
- No live systems were modified and no subagent edited files.
- Created local handoff at
/Users/samaguiar/Documents/Projects/admin/session_logs/opportunities-newest-first-triage-2026-05-31.md.
Main Decision
Newest-to-oldest is the right default because many older entries are already superseded by repo reorgs, WordPress repairs, or changed canonical paths. The refinement is to sort by two keys: freshness first, then live-system risk. Lead intake, Salesforce/Litify data, sync health, and public WordPress issues can outrank newer cosmetic work.
Recommended First Execution Queue
- Google LSA / CallRail / Litify reconcile from 2026-05-28. Current and high operational risk. Needs live CallRail, mailbox, and Salesforce verification.
- Sam Cares and Contact Foundry-orange page-local sweep from 2026-05-31 and 2026-05-28. Current but lower risk. Needs live WordPress source and rendered QA.
- RingCentral to Litify SMS sync health from 2026-04-14. Older but high-risk because live permissions, test records, and Notes were changed.
- WordPress intake relay verification from 2026-04-08 / 2026-04-10. Older but high-risk because it affects lead capture.
- Practice-area trust-strip remaining migration from 2026-04-19, only after a fresh live crawl confirms old
.sa-trust-bar pages remain.
- Litify P05 script fixes from 2026-04-18, after resolving current repo paths and dry-running.
- P04/P12 FLS verification from 2026-04-18, after Tooling API and FLS checks.
- BeforeSave phone-formatting redesign from 2026-04-18 as staged design/test work, not live activation.
- Report inventory cleanup and Business Party name normalization from 2026-04-02 / 2026-04-17, after fresh Salesforce counts.