k8s-documentation

Generate migration_report.md with runbooks, risk registers, and deployment guidance for AKS conversions.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/Dongbumlee/container-migration-copilot --skill k8s-documentation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: k8s-documentation
Source: https://github.com/Dongbumlee/container-migration-copilot/tree/main/.github/plugins/container-migration/skills/k8s-documentation
Command: npx skills add https://github.com/Dongbumlee/container-migration-copilot --skill k8s-documentation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate comprehensive migration documentation that captures every decision, conversion detail, risk, and deployment step from a container migration to AKS.

Core Features & Use Cases

  • Generate migration_report.md with sections for executive summary, platform assessments, file-by-file conversion details, runbooks, risk registers, and references
  • Enforce markdown quality and consistency across the documentation artifacts
  • Produce operator-ready deployment runbooks and validation steps for AKS migrations

Quick Start

Run the documentation generator on your converted artifacts to produce a complete migration_report.md.

Frequently Asked Questions about k8s-documentation

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

FAQPage Schema
How do I generate Kubernetes migration documentation for an AKS deployment runbook?

You can generate Kubernetes migration documentation by processing container-to-AKS conversion artifacts. This automatically produces a production-ready deployment runbook, capturing decision logs, risk assessments, and validation steps in a markdown report.

What should be included in an AKS migration risk assessment and source platform assessment?

An AKS migration risk assessment should include a comprehensive risk register and source platform evaluation. The documentation covers Executive Summary, Source Platform Assessment, Target Architecture, and File-by-File Conversion Details to ensure complete migration tracking.

Can I use this to document EKS, GKE, OpenShift, Rancher, Tanzu, and on-prem to AKS migrations?

Yes, you can document migrations from EKS, GKE, OpenShift, Rancher, Tanzu, and on-prem platforms to AKS. It processes conversion artifacts from these source platforms to produce standardized deployment guidance and decision logs.

How do I create file-by-file conversion details for a Kubernetes workload migration?

You create file-by-file conversion details by running the documentation generator on your existing conversion artifacts. It maps each file change and automatically formats the details into a structured migration_report.md alongside the runbook and risk register.

What is the best way to automate deployment guidance and decision logs for AKS migrations?

The best way to automate deployment guidance is by processing conversion artifacts through a documentation generator. This enforces markdown quality and consistency while producing operator-ready runbooks, decision logs, and references without manual formatting.