sample-oh-my-aidlcops

AIDLC × AgenticOps — a plugin marketplace that automates the full AI-Driven
Development Lifecycle with agent-based operations on AWS.

한국어 README · Documentation · Plugins · Steering

What is OMA?

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.

Who is this for?

• Platform engineers building agentic AI on AWS EKS.
• Teams running LLM/agent workloads who want AIDLC to cover operations, not
  just design and construction.
• Teams modernizing legacy workloads onto AWS using a repeatable 6R workflow.
• Claude Code or Kiro users who want a drop-in marketplace rather than
  hand-rolling skills.

Plugins

Tier-0 workflows

OMA inherits the Tier-0 pattern from OMC — high-leverage workflows you invoke
once and let run, with human approval only at checkpoints.

Install

⚡ One-liner (Tech Preview — recommended)

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.1 stabilizes profile.yaml v1
and the 6 ontology schemas. Everything else (CLI UX, DSL fields, doctor
report shape) may evolve before GA. See Support Policy.

Claude Code (native marketplace)

claude
> /plugin marketplace add https://github.com/aws-samples/sample-oh-my-aidlcops
> /plugin install agentic-platform agenticops aidlc-inception aidlc-construction modernization

Claude Code (manual)

git clone https://github.com/aws-samples/sample-oh-my-aidlcops
bash sample-oh-my-aidlcops/scripts/install/claude.sh

Kiro

git clone https://github.com/aws-samples/sample-oh-my-aidlcops
bash sample-oh-my-aidlcops/scripts/install/kiro.sh

Initialize .omao/ in your project

cd <your-project>
bash <path-to-oma>/scripts/init-omao.sh

AIDLC extensions (opt-in)

bash scripts/install/aidlc-extensions.sh
# Clones awslabs/aidlc-workflows into ~/.aidlc and symlinks OMA's opt-in extensions.

Liked it? Give the repo a Star

If OMA was useful, a ⭐ on the GitHub repository
helps us prioritize maintenance and keeps release notifications flowing
to you. It is entirely optional — nothing in the CLI changes based on
your star status.

Architecture

User request
    │
    ▼
Tier-0 trigger  ─── matches keyword? ──▶ /oma:<workflow>
    │
    ▼
Plugin dispatch
    │
    ├─▶ agentic-platform    (build)
    ├─▶ agenticops          (operate)
    ├─▶ aidlc-inception     (Phase 1)
    ├─▶ aidlc-construction  (Phase 2)
    └─▶ modernization       (legacy → AWS)
    │
    ▼
Skills execute, calling AWS Hosted MCP
    │
    ├─▶ eks, cloudwatch, prometheus, aws-iac, cost-explorer, ...
    │
    ▼
Checkpoint — human approves
    │
    ▼
Operations phase continues autonomously
    │
    └─▶ self-improving-loop feeds corrections back to Construction

Foundation: ontology + harness DSL

OMA plugins rest on two shared layers:

1. Ontology (ontology/, schemas/ontology/) — six JSON Schemas that
   define the vocabulary every plugin and skill agrees on: Agent, Skill,
   Deployment, Incident, Budget, Risk. A handoff between Construction
   and Operations is no longer a prose description; it is a validated
   Deployment document. See ontology/README.md and
   ontology/glossary.md.
2. Harness DSL (schemas/harness/dsl.schema.json, tools/oma_compile/) —
   one <plugin>.oma.yaml per plugin is the single source of agents, MCP
   servers, hooks, and triggers. python -m tools.oma_compile translates it
   to the native .mcp.json and kiro-agents/*.agent.json files that Claude
   Code and Kiro already consume, so marketplace installs stay unchanged.

<plugin>.oma.yaml  ──(oma-compile)──▶  .mcp.json
                                   ▶  kiro-agents/<agent>.agent.json
                                   ▶  .omao/triggers.json  (merged across plugins)

CI (.github/workflows/oma-foundation.yml) validates every schema fixture and
runs oma-compile --check to reject drift between DSL sources and committed
native files.

Security posture

This repository ships with conservative defaults. A few things are worth
calling out before you use it in production:

• MCP servers are pinned to exact PyPI versions in every .mcp.json and
  kiro-agents/*.agent.json. @latest is not used anywhere — a compromised
  upstream release cannot silently land alongside AWS credentials.
• EKS MCP is read-only by default. The bundled Kiro agent profile does
  not pass --allow-write or --allow-sensitive-data-access to
  awslabs.eks-mcp-server. Add them explicitly when you need to provision
  or mutate EKS resources, and audit that change.
• IAM is least-privilege. The langfuse-observability skill uses a
  customer-managed policy scoped to the Langfuse bucket ARN; AWS managed
  AmazonS3FullAccess (s3:* account-wide) is explicitly rejected with a
  "Bad Example" block in the skill.
• budget.yaml expressions are sandboxed. The cost-governance skill
  evaluates rule["when"] via simpleeval
  (AST walker, zero builtins, zero callables). A documented Bad Example shows
  why Python eval() on a user-editable file is an RCE vector.
• Session state stays local. .omao/state/, .omao/plans/, .omao/logs/,
  .omao/notepad.md, and .omao/project-memory.json are gitignored —
  audit-trail captures prompts verbatim (PII, approver identity, SOC2
  retention content) and must never leave the machine.
• Hooks require a real JSON encoder. hooks/session-start.sh uses jq
  (with python3 / python as ordered fallbacks) and exits non-zero rather
  than emitting shell-interpolated JSON, preventing state-file injection into
  the session context.

Reused assets

OMA stands on top of existing AWS and community work rather than reinventing.

Full attribution in NOTICE.

License

MIT No Attribution (MIT-0). See LICENSE.

Contributing

OMA is in Tech Preview (v0.2.0-preview.1). See CONTRIBUTING.md for the bug
report and pull request process, and CODE_OF_CONDUCT.md
for the Amazon Open Source Code of Conduct. Issues and PRs are especially
welcome for skill quality, MCP coverage gaps, and Kiro compatibility testing.

For security issues, do not open a public GitHub issue — follow the AWS
vulnerability reporting process
instead.