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
hex-upgrade-migrationAnalyze, plan, and execute Hex SDK upgrades with breaking change detection. Use when upgrading Hex SDK versions, detecting deprecations, or migrating to new API versions. Trigger with phrases like "upgrade hex", "hex migration", "hex breaking changes", "update hex SDK", "analyze hex version".
Independent GitHub snapshot · Automated classification · Original documentation governs
name: hex-upgrade-migration description: 'Analyze, plan, and execute Hex SDK upgrades with breaking change detection.
Use when upgrading Hex SDK versions, detecting deprecations,
or migrating to new API versions.
Trigger with phrases like "upgrade hex", "hex migration",
"hex breaking changes", "update hex SDK", "analyze hex version".
' allowed-tools: Read, Write, Edit, Bash(npm:), Bash(git:) version: 1.6.0 license: MIT author: Jeremy Longshore jeremy@intentsolutions.io tags:
Hex API is versioned at /api/v1/. Monitor the Hex changelog for new endpoints and deprecations.
grep -r "app.hex.tech" src/ --include="*.ts" --include="*.py"
pip install --upgrade airflow-provider-hex
Produce an upgrade receipt with from/to versions, affected contracts, fixture/canary outcomes, aggregate assertions, owner approval, compatibility decision, and rollback revision. Exclude SQL, workspace output, and credentials.
Stop for incompatible parameter/output contracts, authorization drift, unbounded replays, or a failed canary assertion. Restore the exact pinned prior revision and retain redacted evidence rather than forcing migration.
from=client-r12; to=client-r13; sandbox=pass; staging=pass; assertions=pass; canary=held; rollback=r12 is a defensible upgrade record.