Cicd Pipeline

CI/CD Pipeline — Pipeline Design, Build, Monitoring, and Optimization

An agent team collaborates to perform CI/CD pipeline design, configuration generation, security integration, and monitoring in a single pass.

Execution Mode

Agent Team — 5 members communicate directly via SendMessage and cross-validate each other's work.

Agent Composition

Workflow

Phase 1: Preparation (Performed directly by the orchestrator)

1. Extract from user input:
   • Project Type: Language/framework (Node.js, Python, Go, Java, etc.)
   • CI/CD Tool: GitHub Actions / GitLab CI / Jenkins
   • Deployment Target: AWS / GCP / Azure / Kubernetes / Docker
   • Branch Strategy (optional): GitFlow, Trunk-based
   • Existing Files (optional): Existing CI/CD configuration, Dockerfile, etc.
2. Create the _workspace/ directory at the project root
3. Organize the input and save to _workspace/00_input.md
4. If existing files are provided, copy them to _workspace/ and skip the corresponding phase
5. Determine the execution mode based on the scope of the request

Phase 2: Team Assembly and Execution

Tasks 2a (infrastructure) and 2b (security) are executed in parallel.

Inter-team communication flow:

• pipeline-designer completes -> Delivers stage requirements to infra-engineer, scan placement to security-scanner, deployment strategy to monitoring-specialist
• infra-engineer completes -> Delivers log/metric points to monitoring-specialist, image/dependency paths to security-scanner
• security-scanner completes -> Delivers security alert rules to monitoring-specialist
• pipeline-reviewer cross-validates all artifacts. When 🔴 must-fix issues are found, requests revisions from the relevant agent -> rework -> re-verify (up to 2 rounds)

Phase 3: Integration and Final Artifacts

Organize the final artifacts based on the review report:

1. Verify all files in _workspace/
2. Confirm that all 🔴 must-fix items from the review report have been addressed
3. Report the final summary to the user

Mode by Task Scale

Leveraging existing files: If the user provides YAML, Dockerfile, or other existing files, skip the corresponding steps.

Data Transfer Protocol

File naming convention: {order}_{agent}_{artifact}.{extension}

Error Handling

Test Scenarios

Normal Flow

Prompt: "Create a GitHub Actions CI/CD pipeline for a Node.js Express app. I want to deploy to AWS ECS with a Canary deployment strategy" Expected Result:

• Design: CI (lint -> test -> build -> scan) + CD (staging -> approval -> canary -> rollout)
• Infrastructure: GitHub Actions YAML, Dockerfile, ECR config, secret management
• Security: Semgrep + Trivy + Gitleaks configuration
• Monitoring: DORA metrics, build/deploy alerts, dashboards
• Review: All items in the alignment matrix verified

Existing File Flow

Prompt: "Add security scanning to this GitHub Actions config" + YAML file Expected Result:

• Copy existing YAML to _workspace/02_pipeline_config/
• Security mode: deploy security-scanner + pipeline-reviewer
• Skip pipeline-designer, infra-engineer, monitoring-specialist

Error Flow

Prompt: "Create a CI/CD quickly, Python project" Expected Result:

• Deployment target not specified -> Docker-based generic design
• GitHub Actions selected as default
• Review report notes "deployment target unspecified, Docker container-based generic configuration"

Agent Extension Skills

Extension skills that enhance each agent's domain expertise: