spec-migrate-1.0-to-1.1

To upgrade a Project Spec from v1.0 to v1.1, this skill automatically adds the required schemaVersion and idp.realmStrategy fields. It ensures legacy specs become compliant with current DevEnv Agent platform engineering workflows without manual editing.

Your v1.0 Project Spec fails because it lacks mandatory v1.1 fields, specifically schemaVersion and idp.realmStrategy. The spec-migrate skill resolves this compatibility gap automatically by injecting the missing schema requirements during the orchestrator loading process.

Schema compliance for v1.1 Project Specs requires including the schemaVersion and idp.realmStrategy fields. This ensures consistent Spec formatting across all project onboarding workflows and prevents processing failures within platform engineering pipelines.

No, you do not need to manually edit legacy Project Specs to add the idp.realmStrategy field. The skill operates transparently in the background, automatically upgrading outdated v1.0 specs to v1.1 compliance when they are processed.

Yes, you can use existing v1.0 Project Specs with current platform onboarding pipelines by asking the DevEnv Agent to process them. The skill automatically updates the specs to v1.1 compliance so they work seamlessly with current deployment workflows.

You should use automated spec migration for legacy Project Specs when your team has existing v1.0 service definitions that need to integrate with current platform engineering workflows. It applies required v1.1 mandatory fields to prevent onboarding failures.