cloud-native-planner

Generate incremental cloud-native deployment plans for Azure transformation layers.

Updated May 6, 2026
One-click install
npx skills add https://github.com/crgarcia12/compy --skill cloud-native-planner-crgarcia12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cloud-native-planner
Source: https://github.com/crgarcia12/compy/tree/main/.github/skills/cloud-native-planner
Command: npx skills add https://github.com/crgarcia12/compy --skill cloud-native-planner-crgarcia12

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps you plan the journey to cloud-native deployment on Azure by generating increments for containerization, configuration externalization, infrastructure-as-code, observability, CI/CD, and Azure service provisioning.

Core Features & Use Cases

  • Incremental Planning: Generate a sequence of increments to move an application from its current hosting model to a fully cloud-native deployment on Azure.
  • Layered Approach: Follows a fixed ordering of transformation layers: Containerization, Configuration Externalization, Infrastructure-as-Code, Observability, CI/CD Pipeline, and Azure Service Provisioning.
  • Inputs and Outputs: Reads cloud-native assessments, ADRs, architecture maps, and existing outputs to generate increments that feed into the Phase 2 delivery pipeline.

Quick Start

Run the cloud-native-planner skill with the current cloud-native assessment to generate a plan for containerization.

Frequently Asked Questions about cloud-native-planner

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

FAQPage Schema
How do I plan cloud-native deployment on Azure in increments?

Planning cloud-native deployment on Azure in increments requires current cloud-native assessments, ADRs, and architecture maps to generate a phased sequence covering containerization, configuration externalization, infrastructure-as-code, observability, CI/CD, and Azure service provisioning.

What is the layered approach for moving an application to cloud-native on Azure?

The layered approach for cloud-native on Azure follows a fixed ordering of transformation layers: Containerization, Configuration Externalization, Infrastructure-as-Code, Observability, CI/CD Pipeline, and Azure Service Provisioning to incrementally shift hosting models.

What inputs do I need to generate an infrastructure-as-code and CI/CD plan for Azure?

Generating an infrastructure-as-code and CI/CD plan for Azure requires existing cloud-native assessments, ADRs, architecture maps, and existing outputs to formulate the deployment increments for the Phase 2 delivery pipeline.

Can I use this approach for containerization and configuration externalization without existing architecture maps?

No, existing architecture maps and cloud-native assessments are required inputs to generate accurate increments for containerization and configuration externalization during your Azure deployment transformation.

When do I need to generate deployment increments for Azure service provisioning?

You need to generate deployment increments for Azure service provisioning when moving an application from its current hosting model to a fully cloud-native deployment, following the completion of observability and CI/CD pipeline layers.