AI Coding Agents

This document covers AI coding agent strategies for implementing design as code in the AIDLC Construction phase. It focuses on Kiro's Spec-Driven approach, Amazon Q Developer's real-time build and test capabilities, MCP-based context collection, and CI/CD integration patterns.

1. AI Coding Agents Overview

The AIDLC Construction phase transforms Inception phase outputs (requirements, design, ontology) into executable code and infrastructure. AI coding agents automate this transformation and perform the following roles:

1. Requirements → Code Transformation — Convert natural language requirements into structured specifications (Spec), then generate code
2. Real-time Build & Test — Immediately build and test generated code to detect errors early (Loss Function)
3. Security Scanning — Automatically detect and suggest fixes for security vulnerabilities in Kubernetes manifests and application code
4. CI/CD Integration — Automatically integrate with GitOps pipelines like GitHub Actions and Argo CD
5. Real-time Context Collection — Reflect current infrastructure state, costs, and workload information via MCP servers

Amazon Q Developer and Kiro use Anthropic Claude models by default, and Kiro also supports open-weight models for cost optimization and specialized domain extensions.

2. Kiro — Spec-Driven Development

2.1 Spec-Driven Inception

Kiro systematizes Inception phase outputs into Spec files, structuring the entire process from natural language requirements to code.

requirements.md → design.md → tasks.md → code generation → validation

EKS Example: Payment Service Deployment

requirements.md

# Payment Service Deployment Requirements

## Functional Requirements
- REST API endpoint: /api/v1/payments
- Integration with DynamoDB table
- Asynchronous event processing via SQS

## Non-Functional Requirements
- P99 latency: < 200ms
- Availability: 99.95%
- Auto-scaling: 2-20 Pods
- EKS 1.35+ compatible

design.md

# Payment Service Architecture

## Infrastructure Configuration
- EKS Deployment (3 replicas min)
- ACK DynamoDB Table (on-demand)
- ACK SQS Queue (FIFO)
- HPA (CPU 70%, Memory 80%)
- Karpenter NodePool (graviton, spot)

## Observability
- ADOT sidecar (traces → X-Ray)
- Application Signals (automatic SLI/SLO)
- CloudWatch Logs (/eks/payment-service)

## Security
- Pod Identity (replaces IRSA)
- NetworkPolicy (namespace isolation)
- Secrets Manager CSI Driver

tasks.md

# Implementation Tasks

## Bolt 1: Infrastructure
- [ ] Write ACK DynamoDB Table CRD
- [ ] Write ACK SQS Queue CRD
- [ ] Define KRO ResourceGroup (integrate DynamoDB + SQS)
- [ ] Configure Karpenter NodePool (graviton, spot)

## Bolt 2: Application
- [ ] Implement Go REST API
- [ ] Integrate DynamoDB SDK
- [ ] Implement SQS consumer
- [ ] Dockerfile + multi-stage build

## Bolt 3: Deployment
- [ ] Write Helm chart
- [ ] Define Argo CD Application
- [ ] Write HPA manifest
- [ ] Write NetworkPolicy

## Bolt 4: Observability
- [ ] Configure ADOT sidecar
- [ ] Add Application Signals annotation
- [ ] Create CloudWatch dashboard
- [ ] Set up SLO alerts

2.2 Spec-Driven vs. Directive Approach

Core Value of Spec-Driven

Directive Approach: "Create DynamoDB" → "Need SQS too" → "Now deploy" → Manual instructions each time, risk of context loss

Spec-Driven: Kiro analyzes requirements.md → generates design.md → breaks down tasks.md → auto-generates code → connects to validation with consistent Context Memory

The Spec-Driven approach maintains the full context and can automatically track the scope of impact when requirements change. For DDD (Domain-Driven Design) integration patterns, see DDD Integration.

2.3 MCP Native Architecture

Kiro is designed MCP (Model Context Protocol) native, collecting real-time infrastructure state via AWS Hosted MCP servers during the Inception phase.

[Kiro + MCP Interaction]

Kiro: "Check EKS cluster status"
  → EKS MCP Server: get_cluster_status()
  → Response: { version: "1.35", nodes: 5, status: "ACTIVE" }

Kiro: "Analyze costs"
  → Cost Analysis MCP Server: analyze_cost(service="EKS")
  → Response: { monthly: "$450", recommendations: [...] }

Kiro: "Analyze current workload"
  → EKS MCP Server: list_deployments(namespace="payment")
  → Response: { deployments: [...], resource_usage: {...} }

This enables realistic designs reflecting current infrastructure state and costs when generating design.md. For details on MCP integration architecture, refer to the AIDLC MCP strategy document.

2.4 Open-Weight Model Support

Kiro supports open-weight models (Llama 3.1 405B, Mixtral 8x22B, DeepSeek R1, etc.) in addition to Claude, providing the following benefits:

• Cost Optimization — Process simple code generation tasks with smaller models (1/10 token cost)
• Specialized Domain Extension — Utilize domain-specific fine-tuned models for finance, healthcare, etc.
• On-Premises Deployment — Perform inference within EKS clusters without sending sensitive data externally

For open-weight model deployment strategies, see Open-Weight Models.

3. Amazon Q Developer — Real-time Build and Test

AWS announced Amazon Q Developer's real-time code execution capability in February 2025. This is an innovative approach where AI generates code, then automatically builds and runs tests to validate results before presenting to developers.

It's a core mechanism in the AIDLC Construction phase for activating the Loss Function early to prevent errors from propagating downstream.

3.1 Real-time Code Execution Mechanism

Traditional AI coding tools required developers to manually build and test after code generation. Q Developer automates this process.

Traditional Approach:
  AI code generation → developer manual build → developer manual test → error discovery → feedback to AI → regeneration
  (iteration cycle: 5-10 minutes)

Q Developer Real-time Execution:
  AI code generation → automatic build → automatic test → result validation → (auto-retry on error) → developer review
  (iteration cycle: 1-2 minutes, minimal developer intervention)

Core Mechanisms

1. Automatic Build Pipeline

   • Automatically execute project build tools (Maven, Gradle, npm, pip, etc.)
   • Immediately detect compilation errors and dependency conflicts
   • On build failure, analyze error messages and automatically retry code fixes

2. Automatic Test Execution

   • Automatically run unit tests and integration tests
   • On test failure, analyze failure causes and fix code or tests
   • Maintain existing test coverage while adding new code

3. Validation Before Developer Review

   • Developer receives code that has already passed build and tests
   • Developer focuses on business logic and design review (Loss Function role)
   • Validates "Is this the right code?" not "Does the code work?"

3.2 Automatic Security Scan Fixes

Q Developer automatically scans Kubernetes YAML and application code for security vulnerabilities and provides fix suggestions.

Kubernetes YAML Security Scan

1. Root Privilege Detection — Detects runAsUser: 0 or runAsNonRoot: false, suggests runAsUser: 1000, runAsNonRoot: true
2. Privileged Container Detection — Detects securityContext.privileged: true, suggests explicitly adding only necessary capabilities
3. Missing securityContext Detection — When Pod/Container lacks securityContext, suggests settings following least privilege principle

Automatic Fix Suggestion Example

# Problem detected by Q Developer
apiVersion: v1
kind: Pod
metadata:
  name: payment-pod
spec:
  containers:
    - name: payment
      image: payment:v1
      securityContext:
        runAsUser: 0  # ⚠️ Using root privileges
        privileged: true  # ⚠️ Privileged mode

# Fix suggested by Q Developer
apiVersion: v1
kind: Pod
metadata:
  name: payment-pod
spec:
  securityContext:
    runAsNonRoot: true
    runAsUser: 1000
    fsGroup: 1000
    seccompProfile:
      type: RuntimeDefault
  containers:
    - name: payment
      image: payment:v1
      securityContext:
        allowPrivilegeEscalation: false
        readOnlyRootFilesystem: true
        capabilities:
          drop:
            - ALL
          add:
            - NET_BIND_SERVICE  # Add only necessary capabilities

3.3 Feedback Loop Reduction Effect

Traditional Construction Phase:
  [Developer] Write code (30 min)
    → [Developer] Manual build (2 min)
    → [Developer] Manual test (5 min)
    → [Developer] Discover errors (10 min debugging)
    → [Developer] Fix code (20 min)
    → Repeat...
  Total time: 2-3 hours

Q Developer Real-time Execution:
  [AI] Code generation (1 min)
    → [AI] Automatic build & test (30 sec)
    → [AI] Error detection and automatic fix (1 min)
    → [Developer] Loss Function validation (10 min)
    → [Argo CD] Automatic deployment
  Total time: 15-20 minutes

Q Developer's Value in AIDLC

Q Developer's real-time execution implements AIDLC's core principle of "Minimize Stages, Maximize Flow". By automating each stage of code generation → build → test → validation, it eliminates handoffs, allowing developers to focus only on decision-making (Loss Function). This is the core mechanism that reduces traditional SDLC's week/month cycles to AIDLC's hour/day cycles.

4. AI Coding Agent Comparison

AI Coding Agents

Amazon Q Developer, Kiro, Claude Code, Cursor, OpenAI Codex

Amazon Q Developer Key Features

Code Generation

Auto-generate AWS SDK, CDK, Terraform code

Security Scan

Automated code vulnerability detection

Code Transform

Java 8→17, .NET Framework→.NET Core, etc.

CloudWatch Investigations

AI-powered operational issue analysis

EKS Troubleshooting

kubectl command suggestions, YAML error fixes

Amazon Q Developer

Provider: AWS

Model: Claude (Anthropic)

AWS Services★★★★★

Spec-driven★★☆☆☆

Security Scan★★★★★

MCP Integration★★★★☆

EKS Ops★★★★★

Cost: Pro $19/mo

Specialty: AWS Native + Security

Kiro

Provider: AWS

Model: Claude + Open Weight

AWS Services★★★★☆

Spec-driven★★★★★

Security Scan★★★☆☆

MCP Integration★★★★★

EKS Ops★★★★☆

Cost: Separate

Specialty: Spec-driven + MCP Native

Claude Code

Provider: Anthropic

Model: Claude Opus/Sonnet

AWS Services★★★☆☆

Spec-driven★★★☆☆

Security Scan★★★☆☆

MCP Integration★★★★★

EKS Ops★★★★☆

Cost: Max $100-200/mo

Specialty: Autonomous Agent + MCP

Cursor

Provider: Anysphere

Model: Claude / GPT-4o / Custom

AWS Services★★☆☆☆

Spec-driven★★★☆☆

Security Scan★★☆☆☆

MCP Integration★★★★☆

EKS Ops★★☆☆☆

Cost: Pro $20/mo

Specialty: IDE Integration + Multi-model

OpenAI Codex

Provider: OpenAI

Model: codex-1 (o3-mini based)

AWS Services★★☆☆☆

Spec-driven★★☆☆☆

Security Scan★★★☆☆

MCP Integration★★☆☆☆

EKS Ops★★☆☆☆

Cost: Included in Pro $20/mo

Specialty: Multi-file Autonomous Coding

Selection Guide: For AWS-native development and security scanning, use Q Developer. For systematic Spec-driven workflows, choose Kiro. For MCP-based autonomous agents, use Claude Code. For IDE-integrated multi-model development, try Cursor. For multi-file autonomous coding, consider OpenAI Codex. Q Developer, Kiro, and Claude Code all use Anthropic Claude models, and Kiro also supports open weight models for cost optimization and domain-specific extensibility.

5. MCP-Based Real-time Context Collection

Kiro's MCP native architecture collects real-time infrastructure state via AWS Hosted MCP servers during the Construction phase to reflect in design.

5.1 AWS Hosted MCP Server Utilization

EKS MCP Server

// Kiro queries EKS cluster status in real-time
const cluster = await mcp.call('eks-mcp-server', 'get_cluster_status', {
  clusterName: 'prod-eks'
});

// Response: { version: "1.35", nodes: 5, status: "ACTIVE", capacityType: "SPOT" }
// → Reflects current cluster version when generating design.md

Cost Analysis MCP Server

// Optimize design with cost analysis
const cost = await mcp.call('cost-analysis-mcp', 'analyze_cost', {
  service: 'EKS',
  timeRange: 'last_30_days'
});

// Response: { monthly: "$450", recommendations: ["Use Spot for dev clusters", "Enable Karpenter consolidation"] }
// → Reflects cost optimization strategies in design.md

Workload MCP Server

// Determine resource allocation with current workload analysis
const workload = await mcp.call('eks-mcp-server', 'list_deployments', {
  namespace: 'payment'
});

// Response: { deployments: [...], resource_usage: { cpu: "60%", memory: "75%" } }
// → Used to determine HPA thresholds and NodePool settings

5.2 MCP Integration Benefits

1. Context-Based Design — Generate realistic designs reflecting current infrastructure state
2. Cost Optimization — Automatically suggest cost reduction strategies like Spot and Graviton based on actual usage patterns
3. Resource Efficiency — Optimize HPA and Karpenter settings based on current workload state
4. Consistency Assurance — Minimize gap between design and reality with real-time data

6. CI/CD Integration

Integrate AI coding agents into CI/CD pipelines to implement Quality Gate automation.

6.1 GitHub Actions Integration

# .github/workflows/aidlc-construction.yml
name: AIDLC Construction Quality Gate
on:
  pull_request:
    types: [opened, synchronize]

jobs:
  q-developer-validation:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      # 1. Q Developer Security Scan
      - name: Q Developer Security Scan
        uses: aws/amazon-q-developer-action@v1
        with:
          scan-type: security
          source-path: .
          auto-fix: true  # Apply automatic fix suggestions

      # 2. Real-time Build and Test
      - name: Q Developer Build & Test
        uses: aws/amazon-q-developer-action@v1
        with:
          action: build-and-test
          test-coverage-threshold: 80

      # 3. Kubernetes Manifest Validation
      - name: K8s Manifest Security Check
        run: |
          kube-linter lint deploy/ --config .kube-linter.yaml

      # 4. Allow Argo CD Sync Only on Pass
      - name: Approve for GitOps
        if: success()
        run: echo "Quality Gate passed. Ready for Argo CD sync."

6.2 Argo CD Integration

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: payment-service
  namespace: argocd
spec:
  project: default
  source:
    repoURL: https://github.com/org/payment-service
    targetRevision: main
    path: deploy/
  destination:
    server: https://kubernetes.default.svc
    namespace: payment
  syncPolicy:
    automated:
      prune: true
      selfHeal: true
    syncOptions:
      - CreateNamespace=true
    # Sync only when Quality Gate passes
    retry:
      limit: 3
      backoff:
        duration: 5s
        factor: 2
        maxDuration: 3m

6.3 Quality Gate Workflow

1. PR Creation — Developer submits Kiro-generated code as PR
2. Security Scan — Q Developer scans Kubernetes manifests and application code
3. Build & Test — Q Developer automatically builds and runs tests
4. Validation Pass — Argo CD automatically syncs when all checks pass
5. Deployment Complete — Deploys to EKS cluster, Application Signals automatically enabled

This workflow is a core implementation pattern of Harness Engineering.

7. Agent Selection Guide

AI coding agent selection criteria by project characteristics.

7.1 By Project Scale

Project Scale	Recommended Agent	Reason
Small (1-5 microservices)	Amazon Q Developer	IDE integration, fast feedback, security scan
Medium (5-20 microservices)	Kiro + Q Developer	Spec-Driven consistency, Q Developer real-time validation
Large (20+ microservices)	Kiro + Open-Weight Models	Cost optimization, domain-specialized model utilization

7.2 By Domain

Domain	Recommended Agent	Reason
General Web Applications	Amazon Q Developer	General language/framework support, rapid prototyping
EKS Infrastructure Automation	Kiro + MCP	Reflect real-time cluster state, ACK/KRO integration
Finance/Healthcare Specialized Domains	Kiro + Fine-tuned Open Models	Regulatory compliance, on-premises deployment
Legacy Migration	Amazon Q Developer /transform	Automatic Java 8→17, .NET Framework→Core conversion

7.3 By Team Maturity

Team Maturity	Recommended Agent	Reason
First AI Tool Adoption	Amazon Q Developer	IDE integration, low learning curve, AWS official support
DevOps Skilled Team	Kiro + Q Developer	Spec-Driven structure, CI/CD automation, MCP utilization
AI Platform Operations Team	Kiro + Open-Weight Models	Custom model deployment, cost optimization, special requirements

7.4 Cost Considerations

Monthly Request Volume	Recommended Strategy	Estimated Cost
< 10,000 requests	Amazon Q Developer only	~$50-100
10,000 - 100,000 requests	Kiro + Claude (simple tasks use smaller models)	~$200-500
> 100,000 requests	Kiro + Open-Weight Models (EKS self-hosting)	~$100-300 (infrastructure cost)

8. Practical Application Patterns

8.1 Hybrid Strategy

For most teams, Amazon Q Developer + Kiro hybrid is optimal:

1. Early Development — Rapid prototyping with Q Developer, real-time feedback
2. After Design Confirmation — Consistent implementation with Kiro Spec-Driven
3. Security Validation — Early vulnerability detection with Q Developer automatic scan
4. Deployment Automation — Deployment configuration reflecting current cluster state with Kiro MCP

8.2 Ontology-Based Code Generation

When providing Kiro with ontology built during the Inception phase, it generates code reflecting domain terms and relationships:

# ontology.md (provided to Kiro)

## Domain Model
- Payment → Order → Customer
- Payment.status: [pending, completed, failed]
- Payment.method: [card, bank_transfer, wallet]

## Business Rules
- When creating Payment, Order.status must be "confirmed"
- Payment.amount must match Order.total_amount
- On Payment failure, send to SQS retry queue (max 3 times)

Kiro generates design.md and code based on this ontology, ensuring domain term consistency.

8.3 Continuous Learning

AI coding agents progressively improve by learning from team code review feedback:

1. Code Review Feedback — Learn team coding conventions through PR comments
2. Ontology Updates — Update ontology.md when new domain concepts are added
3. MCP Server Extension — Integrate MCP servers when new infrastructure services are added
4. Fine-tuning — Fine-tune open-weight models with team codebase (optional)

References

• AWS DevOps Blog: Enhancing Code Generation with Real-Time Execution in Amazon Q Developer (2025-02-06)
• Amazon Q Developer Official Documentation
• Model Context Protocol (MCP) Specification
• Open-Weight Model Deployment Guide
• DDD Integration
• Harness Engineering