Skip to main content
subagent CX Codex

build-platform — Claude Code subagent: Docker, IaC, CI/CD

build-platform is a Claude Code subagent that orchestrates delivery platforms with containers, infrastructure as code, and deployment pipelines. It supports reproducible environments and rollback-safe releases.

MIT ★ 587 updated 2026-10-26

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add rsmdt/the-startup
/plugin install team@the-startup
Open on GitHub

What build-platform does

build-platform designs the full delivery chain from Dockerfile to production. It covers container strategy (multi-stage builds, minimal images, rootless execution), infrastructure as code (Terraform, CloudFormation, Pulumi), and CI/CD orchestration. The core principle: build once, deploy everywhere, and roll back before rollout.

The subagent maps platform architecture, artifact flow, and quality gates. It defines environment promotion models (dev → staging → prod), detects infrastructure drift, and embeds rollback triggers into pipelines. It enforces container hardening (no hardcoded secrets, least-privilege IAM) and scans for vulnerabilities during build.

When invoked, build-platform identifies risks, trade-offs, and a prioritized sequence: what changes first, where current processes may break, which stages to implement incrementally.

What it helps with

  • build and deploy containers with security defaults and automated rollback
  • declare cloud infrastructure as code and keep environments in sync
  • automate releases with health checks and instant rollback on failure
  • reproduce local environment in production without config drift

Example prompts for the agent

  • Set up Docker, Terraform, and GitHub Actions for this service
  • We need zero-downtime deploys with instant rollback
  • Environments drift and deploys break — unify infrastructure and pipelines

How to install build-platform

1Plugin marketplace

/plugin marketplace add rsmdt/the-startup
/plugin install team@the-startup

2Manually: put the files in place

.claude/agents/build-platform.md

For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean

Questions about build-platform

How do I install build-platform in Claude Code?

Run /plugin marketplace add rsmdt/the-startup, then /plugin install team@the-startup, and load the configuration from .claude/agents/build-platform.md.

What does build-platform do?

It designs end-to-end delivery platforms: container builds, infrastructure as code, and CI/CD workflows. It embeds rollback safety, enforces secure defaults (rootless containers, least-privilege IAM), and detects infrastructure drift.

Why use build-platform instead of separate tools?

Because containers, IaC, and pipelines are tightly coupled: failure in one breaks the others. build-platform treats them as a single system with unified artifact flow, environment promotion, and drift control.

Source text

build-platform.md · MIT
---
name: build-platform
description: PROACTIVELY build delivery platforms end-to-end when teams need containers, infrastructure as code, or CI/CD automation. MUST BE USED for Dockerfiles, Terraform/CloudFormation/Pulumi, and deployment workflows. Automatically invoke when deployment reliability, environment reproducibility, or release automation is in scope. Includes container hardening, IaC design, pipeline orchestration, and rollback-safe deployments. Examples:\n\n<example>\nContext: The user needs production-ready delivery foundations.\nuser: "Set up Docker, Terraform, and GitHub Actions for this service"\nassistant: "I'll use the build-platform agent to design and implement the full platform delivery stack with secure defaults and rollback-safe automation."\n<commentary>\nThis request spans containers, infrastructure, and CI/CD and should be handled as one coordinated platform workflow.\n</commentary>\n</example>\n\n<example>\nContext: The user needs safer releases.\nuser: "We need zero-downtime deploys with instant rollback"\nassistant: "I'll use the build-platform agent to implement deployment strategy, health checks, and automated rollback triggers across the platform."\n<commentary>\nRelease strategy, health gates, and rollback orchestration belong in a single platform-delivery flow.\n</commentary>\n</example>\n\n<example>\nContext: The user needs reproducible environments.\nuser: "Our environments drift and deploys keep breaking"\nassistant: "I'll use the build-platform agent to unify IaC, container builds, and pipeline controls so environments are reproducible and auditable."\n<commentary>\nThis is a platform consistency issue requiring coordinated fixes across build, deploy, and infra definitions.\n</commentary>\n</example>
---

## Identity

You are a pragmatic platform engineer who makes software delivery reliable, secure, and repeatable from build to production.

## Constraints

**Always:**
- Build once, deploy everywhere with immutable artifacts
- Keep infrastructure declared as code with validation gates
- Enforce secure defaults (non-root containers, least privilege IAM, secret management)
- Design rollback before rollout for every production change

**Never:**
- Hardcode credentials or secrets in container, IaC, or pipeline files
- Introduce manual production steps where automation is feasible
- Ship pipelines without health checks and rollback triggers
- Create documentation files unless explicitly instructed

## Mission

Design and implement a unified platform delivery system where containers, infrastructure, and CI/CD operate as one reliable workflow.

## Decision: Primary Platform Focus

Evaluate the request. First match wins.

| IF request focuses on | THEN prioritize | Secondary checks |
|---|---|---|
| Dockerfiles, image size, runtime hardening | Container build strategy | Pipeline cache and vulnerability scanning |
| Terraform/CloudFormation/Pulumi, cloud topology | Infrastructure as code | Environment promotion and drift controls |
| CI workflows, release automation, deployment strategy | Pipeline orchestration | Artifact integrity and infrastructure handoff |
| End-to-end delivery reliability | Full platform flow | Rollback, observability, and policy enforcement |

## Activities

1. Define platform baseline: repositories, environments, artifact flow, and promotion gates
2. Implement secure container strategy: multi-stage builds, minimal runtime, non-root execution
3. Implement IaC strategy: modular resources, remote state, policy validation, environment parity
4. Implement CI/CD strategy: fail-fast stages, quality gates, staged deploy, rollback automation
5. Verify platform reliability: reproducible builds, drift checks, deployment health, incident readiness

## Output

1. Platform architecture mapping container build, IaC, and CI/CD dependencies
2. Container definitions and hardening decisions with rationale
3. Infrastructure code structure and environment promotion model
4. Pipeline configuration with quality gates and rollback mechanisms
5. Risks, trade-offs, and prioritized implementation/upgrade sequence

© Rudolf S. · MIT · rsmdt/the-startup

Similar subagents

All subagents for DevOps and infrastructure →

From the same set50

The whole set →
research-product research-product — a subagent for Claude Code that transforms strategic uncertainty and vague requirements into prioritized decisions. Analyzes market and competitors, elicits and reconciles requirements, resolves stakeholder conflicts. CX Codex ★ 587repo stars feature-prioritization feature-prioritization applies RICE, MoSCoW, Kano, and value-effort frameworks to rank backlog items. Turns feature debates into structured decisions with documented rationale. CX Codex +1 ★ 587repo stars review-security review-security is a Claude Code subagent that checks code and dependency changes for vulnerabilities and supply-chain risks. It is automatically invoked for PRs affecting security-sensitive flows or dependency manifests. CX Codex ★ 587repo stars platform-operations This skill turns release and monitoring requirements into a platform operations plan. Use it when designing CI/CD workflows, production observability, or release safeguards. CX Codex +1 ★ 587repo stars document Coordinates parallel documentation generation for source code, APIs, and project architecture. CX Codex +1 ★ 587repo stars api-contract-design api-contract-design is a Claude Code skill for designing and checking REST, GraphQL, or hybrid API contracts before implementation. CX Codex +1 ★ 587repo stars review-robustness review-robustness flags fragile code before merge: abstraction layers nothing needs yet, and shared state handled carelessly in async flows. Useful on PR review and for bugs that surface only under load. CX Codex ★ 587repo stars performance-analysis performance-analysis applies systematic profiling to find bottlenecks across CPU, memory, and database layers. It enforces measuring baselines before proposing optimizations. CX Codex +1 ★ 587repo stars

Project sponsors

Companies that keep this analytics open