Sails Program Evolution

Overview

Plan how a released Sails contract evolves after deployment.

Use this skill when the work is no longer just “implement a feature”, but instead requires thinking about versioning, compatibility, cutover, ReadOnly handling, frontend/indexer impact, or migration from V1 to V2.

Start Here

Read ../../references/contract-interface-evolution.md, ../../references/gear-sails-production-patterns.md, ../../references/sails-idl-client-pipeline.md, and ../../references/sails-program-and-service-architecture.md.

Use ../../assets/architecture-template.md for the architecture note and ../../assets/task-plan-template.md for the ordered task plan.

Write outputs to:

• docs/plans/YYYY-MM-DD-<topic>-architecture.md
• docs/plans/YYYY-MM-DD-<topic>-tasks.md