executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
hootsuite-upgrade-migrationAnalyze, plan, and execute Hootsuite SDK upgrades with breaking change detection. Use when upgrading Hootsuite SDK versions, detecting deprecations, or migrating to new API versions. Trigger with phrases like "upgrade hootsuite", "hootsuite migration", "hootsuite breaking changes", "update hootsuite SDK", "analyze hootsuite version".
Independent GitHub snapshot · Automated classification · Original documentation governs
name: hootsuite-upgrade-migration description: 'Analyze, plan, and execute Hootsuite SDK upgrades with breaking change detection.
Use when upgrading Hootsuite SDK versions, detecting deprecations,
or migrating to new API versions.
Trigger with phrases like "upgrade hootsuite", "hootsuite migration",
"hootsuite breaking changes", "update hootsuite SDK", "analyze hootsuite version".
' allowed-tools: Read, Write, Edit, Bash(npm:), Bash(git:) version: 1.6.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io tags:
Hootsuite REST API is versioned at /v1/. Monitor the developer changelog for deprecations and new endpoints.
# List all Hootsuite API calls in your codebase
grep -r "platform.hootsuite.com" src/ --include="*.ts" --include="*.py"
// If Hootsuite introduces v2 endpoints:
// BEFORE
const response = await fetch('https://platform.hootsuite.com/v1/messages', ...);
// AFTER
const API_VERSION = process.env.HOOTSUITE_API_VERSION || 'v1';
const response = await fetch(`https://platform.hootsuite.com/${API_VERSION}/messages`, ...);
When Hootsuite adds/removes social network support:
const SUPPORTED_NETWORKS = ['TWITTER', 'FACEBOOK', 'INSTAGRAM', 'LINKEDIN', 'PINTEREST', 'YOUTUBE', 'TIKTOK'] as const;
type SocialNetwork = typeof SUPPORTED_NETWORKS[number];
Produce an upgrade receipt with from/to versions, affected contracts, fixture/draft-canary outcomes, approval/audience assertions, owner approval, compatibility decision, and rollback revision. Exclude copy, media, account identities, and credentials.
Stop for incompatible scheduling/approval contracts, account-scope drift, unbounded replay, or a draft-canary that reaches a public path. Restore the pinned prior revision rather than forcing migration.
from=client-r12; to=client-r13; sandbox=pass; staging=pass; draft=pass; public_posts=0; rollback=r12 is a defensible upgrade record.
For CI, see hootsuite-ci-integration.