replatform

Authors IaC, pipelines, and runbooks for on-prem to cloud migrations with human-executed cutover.

1|Updated Jun 27, 2026
One-click install
npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill replatform-vickysrawat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: replatform
Source: https://github.com/vickysrawat/AI-Assisted-development/tree/main/skills/replatform
Command: npx skills add https://github.com/vickysrawat/AI-Assisted-development --skill replatform-vickysrawat

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Moving an application from on-premises hosting to Azure, AWS, or GCP involves risky infrastructure decisions, unverified integration assumptions, and high-stakes cutovers where mistakes cause downtime or data loss. This Skill structures the entire hosting migration so the LLM authors all infrastructure-as-code, configuration, pipelines, and runbooks while a human executes anything touching real infrastructure or data. ## Core Features & Use Cases - 6R posture classification and intake gating: Classifies rehost, replatform, or refactor-for-cloud posture, verifies integrations, and blocks option presentation until the source-context intake gate passes. - Cloud-capability decomposition with IaC authoring: Decomposes the target into compute, data, identity, messaging, secrets, observability, and network capabilities with the landing zone as Tier-0, then authors Bicep, Terraform, ARM, or Pulumi plus CI/CD pipelines. - NFR assurance and Well-Architected grading: Proves the migration is done via measurability-ceilinged NFR assessment, Well-Architected posture reuse, and golden-master behavioral regression, with hard blocks on regulated NFRs. - Use Case: A team moving a .NET application from on-prem IIS and SQL Server to Azure asks the Skill to plan the move; it produces an integration inventory, target architecture documents, Terraform modules, and four human-executable runbooks (migration, reconciliation, cutover, rollback) before any infrastructure is touched. ## Quick Start Ask the assistant to replatform this on-prem application to Azure using Terraform and Azure DevOps, starting with the intake questions and NFR spec.

Frequently Asked Questions about replatform

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

FAQPage Schema
How do I migrate an on-prem application to Azure or AWS?

Use a replatform workflow that classifies your 6R posture, builds an integration inventory, captures an NFR spec, and decomposes the target into cloud capabilities. The LLM authors the IaC, pipelines, and runbooks while a human executes every step touching real infrastructure or data.

What is the difference between rehost, replatform, and refactor-for-cloud?

Rehost is a minimal-change IaaS VM move, replatform adapts the app to managed services and cloud identity, and refactor-for-cloud restructures code for containers or serverless. Refactor-for-cloud overlays a separate rewrite skill that owns the code changes.

Which IaC tools and CI/CD platforms are supported?

The Skill asks at intake and supports Bicep, Terraform, ARM, and Pulumi for IaC, plus Azure DevOps, GitHub Actions, and GitLab for the deployment pipeline. Choices are recorded in the shared migration ledger and drive plan generation.

Does the AI execute the cloud migration automatically?

No. The LLM only authors IaC, configuration, pipelines, and runbooks; a human executes anything touching real infrastructure or data in any environment. Production and regulated workloads are permanently human-executed, and the executor seam denies real actions while the flag is off.

How is migration success verified after cutover?

Success is proven through NFR assurance grading with a measurability ceiling, a Well-Architected posture assembled from app-readiness output, and golden-master behavioral regression. Regulated NFRs below their floor hard-block completion and require a named approver.

Why does the replatform plan stop before presenting cloud options?

Options are blocked until the source-context intake gate passes and the integration inventory is complete. This prevents target recommendations and TCO estimates from being built on unverified integrations or unaccounted source modules.