By aws-samples
Orchestrate full legacy workload modernization to AWS: assess dependencies, risks, and readiness; decide 6R strategy (Rehost/Replatform/Refactor/Repurchase/Retire/Retain) with cost-risk matrix; design ECS/EKS/Serverless architectures with Mermaid diagrams; containerize Node/Python/Java/Go apps into multi-arch secure Dockerfiles; plan Blue-Green/Canary cutovers with DMS sync, SLO rollbacks, and validation checklists.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Decide the 6R modernization pattern — Rehost / Replatform / Refactor / Repurchase / Retire / Retain — using a decision tree and cost/time/risk matrix. Produces a defensible strategy-decision.md that justifies the selected pattern with quantitative evidence. Use after workload-assessment and before to-be-architecture.
Design the target AWS architecture — ECS Fargate / EKS / Serverless choice, VPC topology with public-private-isolated subnets, managed database selection (RDS/Aurora/DynamoDB), IAM boundaries, and observability baseline (CloudWatch, X-Ray, Langfuse). Produces to-be-architecture.md with Mermaid diagram and compliance matrix. Use after modernization-strategy is approved.
Assess legacy workloads before modernization — application dependency graph, database schema, traffic patterns, RTO/RPO, compliance constraints (ISMS-P/PCI-DSS), technical debt scoring, and Five Lenses readiness. Use when starting brownfield migration to AWS and need a data-driven baseline before selecting a 6R pattern.
Containerize legacy applications with production-grade defaults — multi-stage Dockerfile, docker buildx multi-arch (amd64/arm64), Trivy/grype security scanning, Health Check, non-root user, minimal base (distroless/alpine), ECR push automation, and ECS/EKS manifest templates. Use after to-be-architecture is approved and risk-discovery PASSes.
Plan production traffic cutover — Blue/Green, Canary (1%→10%→50%→100%), DNS-based strategies on ALB/Route53. Defines explicit rollback triggers (SLO violation, error rate, p99 latency), data synchronization via DMS zero-downtime migration, and post-cutover validation checklist. Use when containerization is done and production traffic needs to move from legacy to new environment.
AIDLC × AgenticOps — a plugin marketplace that automates the full AI-Driven Development Lifecycle with agent-based operations on AWS.
한국어 README · Documentation · Plugins · Steering
oh-my-aidlcops (OMA) is the sibling project of
oh-my-claudecode (OMC).
Where OMC orchestrates generic Claude Code workflows, OMA specializes in the
AIDLC loop: Inception → Construction → Operations.
The thesis: AIDLC is complete only when operations are agent-automated. OMA fuses the AWS-official AIDLC workflows with an AgenticOps layer (self-improving feedback loops, autonomous deploys, continuous evaluation, incident response, cost governance) so the lifecycle closes itself without human execution at every step.
| Plugin | What it does | Example skills |
|---|---|---|
agentic-platform | Build & run the Agentic AI Platform on EKS | agentic-eks-bootstrap, vllm-serving-setup, inference-gateway-routing, langfuse-observability, gpu-resource-management, ai-gateway-guardrails |
agenticops | Operate it with agents | self-improving-loop, autopilot-deploy, incident-response, continuous-eval, cost-governance, audit-trail |
aidlc-inception | AIDLC Phase 1 extensions | structured-intake, requirements-analysis, user-stories, workflow-planning |
aidlc-construction | AIDLC Phase 2 extensions | component-design, code-generation, test-strategy, risk-discovery, quality-gates |
modernization | Legacy workload modernization to AWS (6R strategy) | workload-assessment, modernization-strategy, to-be-architecture, containerization, cutover-planning |
OMA inherits the Tier-0 pattern from OMC — high-leverage workflows you invoke once and let run, with human approval only at checkpoints.
| Command | Purpose |
|---|---|
/oma:autopilot | Full AIDLC loop autopilot (Inception → Construction → Operations) |
/oma:aidlc-loop | Single-feature AIDLC one-pass |
/oma:agenticops | Operations mode (continuous-eval + incident-response + cost-governance) |
/oma:self-improving | Feedback loop — Langfuse traces to skill/prompt improvement PR |
/oma:platform-bootstrap | 5-checkpoint Agentic AI Platform build on EKS |
/oma:modernize | Legacy workload modernization (6R decision → cutover) |
/oma:review | AIDLC artifact review (ADR, spec, design, PR) |
/oma:cancel | Terminate active Tier-0 mode |
install.sh downloads the pinned release tarball, extracts to ~/.oma, and
symlinks ~/.local/bin/oma. oma setup then writes a project profile,
seeds the ontology, installs the plugins, and runs oma doctor to confirm
the environment.
curl -fsSL https://raw.githubusercontent.com/aws-samples/sample-oh-my-aidlcops/v0.2.0-preview.1/install.sh | bash
cd my-project
oma setup
oma doctor
See the Easy Button docs
for what oma setup writes, how the 12 doctor probes work, and how the
ontology + harness DSL get enforced at runtime.
Tech Preview notice —
v0.2.0-preview.1stabilizesprofile.yamlv1 and the 6 ontology schemas. Everything else (CLI UX, DSL fields, doctor report shape) may evolve before GA. See Support Policy.
claude
Inside the Claude Code session:
/plugin marketplace add https://github.com/aws-samples/sample-oh-my-aidlcops
/plugin install agentic-platform@oh-my-aidlcops
/plugin install agenticops@oh-my-aidlcops
/plugin install aidlc-inception@oh-my-aidlcops
/plugin install aidlc-construction@oh-my-aidlcops
/plugin install modernization@oh-my-aidlcops
/plugin list
/plugin installaccepts a single plugin id per invocation. Pasting the six lines above lets Claude Code run them sequentially. For a shell one-liner, useclaude <<'EOF' ... EOFto feed the commands via stdin.
git clone https://github.com/aws-samples/sample-oh-my-aidlcops
bash sample-oh-my-aidlcops/scripts/install/claude.sh
npx claudepluginhub aws-samples/sample-oh-my-aidlcops --plugin modernizationPrompt optimization skills for Amazon Nova 1 and Nova 2. Provides /nova1-prompt and /nova2-prompt — rewrite or migrate a prompt for a specific Nova generation with the correct inference config, formatting rules, and (for Nova 2) multimodal caveats.
Healthcare and Life Sciences domain skills and MCP tools — genomics, drug discovery, clinical trials, biomarker analysis, medical terminology, and more. Use with the AWS Agent Toolkit for full agent build-and-deploy workflows.
AWS Spark Analysis plugin for Claude Code - troubleshoot Spark workloads on AWS Glue, EMR, and EMR Serverless
Two Claude Code skills for EKS Auto Mode: onboarding guide for newcomers and maintenance playbook for repo maintainers
AIDLC Operations phase automation — self-improving loops, autonomous deploys, continuous evaluation, incident response, and cost governance on AWS. Humans approve at checkpoints; agents execute diagnosis, proposal, and remediation between gates.
AIDLC Operations phase automation — self-improving loops, autonomous deploys, continuous evaluation, incident response, and cost governance on AWS. Humans approve at checkpoints; agents execute diagnosis, proposal, and remediation between gates.
Cloud infrastructure agents — cloud, container, SRE specialists
DevsForge cloud architecture specialist for AWS, Azure, GCP multi-cloud solutions and optimization.
Editorial "DevOps & Cloud" bundle for Claude Code from Antigravity Awesome Skills.
Build, deploy, and operate applications on AWS. Skills to author infrastructure-as-code, use core services, and complete common tasks.
Convert and import infrastructure from Terraform, CDK, ARM, and CloudFormation to Pulumi