aidlc-migrate

Migrate AI-DLC environments from v1 to v2 with preflight validation and verification.

24|2|Updated Nov 6, 2025
One-click install
npx skills add https://github.com/ikeisuke/ai-dlc-starter-kit --skill aidlc-migrate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aidlc-migrate
Source: https://github.com/ikeisuke/ai-dlc-starter-kit/tree/main/skills/aidlc-migrate
Command: npx skills add https://github.com/ikeisuke/ai-dlc-starter-kit --skill aidlc-migrate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, and includes scripts (resource) components.

What problem does it solve?

Migrating AI-DLC environments from v1 to v2 to ensure a smooth upgrade path and preserve data integrity.

Core Features & Use Cases

  • Step-driven migration: detect, execute, and verify using a manifest-driven workflow.
  • Safe config and data migration via dedicated scripts, with rollback and rollback prompts.
  • Version-aware cleanup and verification to ensure v2 readiness and traceability.

Quick Start

Run the migration workflow to detect v1 artifacts and guide you through preflight, execution, and verification.

Frequently Asked Questions about aidlc-migrate

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I safely migrate an AI-DLC environment from v1 to v2?

The migration process uses a manifest-driven workflow to detect v1 artifacts, execute preflight validation, migrate config and data, and perform post-migration verification to ensure v2 readiness.

What is the best way to automate v1 to v2 environment migration in enterprise DevOps workflows?

Automating v1 to v2 environment migration in enterprise DevOps workflows requires step-driven scripts that manage resource handling, version-aware cleanup, and verification to guarantee traceability throughout the upgrade path.

Do I need to install jq and git to run AI-DLC migration scripts?

Yes, you need jq and git installed as dependencies to run the manifest-driven migration scripts, manage resource handling, and execute safe-branch operations during the v2 upgrade.

Can I rollback a failed v1 to v2 AI-DLC migration?

Yes, you can rollback a failed v1 to v2 AI-DLC migration because the workflow provides rollback prompts and suggestions to safely revert configuration and data changes.

How does manifest-driven resource handling work for AI-DLC environment upgrades?

Manifest-driven resource handling works by using a defined manifest to guide dedicated scripts through preflight checks, data execution, and version-aware cleanup, ensuring that all v1 artifacts are correctly migrated and verified for v2 readiness.