Migrating to Atmos

Overview

Use this skill to adopt Atmos for infrastructure orchestration, general-purpose task running, or tool-version management. Select the migration path from the user's goal and existing tools.

For Make, Just, and Task, assume the user is adopting Atmos as a task runner for application builds, tests, scripts, releases, and other automation. Custom commands need only atmos.yaml; do not introduce Terraform components, stacks, .tfvars conversion, or cloud credentials unless the user separately requests infrastructure orchestration. Preserve the commands behind the tasks, and let Atmos call the existing task runner while individual tasks are migrated.

For Terraform repositories, Atmos can adopt the existing file layout. Start with the smallest change that gives value and add structure as needed.

For Fogg, read from-fogg.md before applying generic Terraform advice: keep generated files for adoption, then take ownership of configuration generation and checks so future changes no longer require Fogg.