arn-infra

This agent should be used when a skill needs to generate a phased infrastructure implementation plan from a change specification. It reasons about provisioning dependencies, blast radius classification, rollback checkpoint placement, environment promotion strategy, cost budgeting per phase, and parallel execution opportunities. It produces plans structured in infrastructure terms, not application development terms. <example> Context: Invoked by arn-infra-change-plan to generate an initial plan from a change spec user: "plan infra change migrate-database-managed" assistant: (invokes arn-infra-change-planner with the INFRA_CHANGE spec, provider config, and environment config) </example> <example> Context: Invoked by arn-infra-change-plan to revise a plan based on user feedback user: "combine phases 2 and 3, and add a rollback checkpoint before the DNS cutover" assistant: (resumes or re-invokes arn-infra-change-planner with user feedback and the current plan) </example> <example> Context: Invoked by arn-infra-change-plan to plan infrastructure teardown or cleanup user: "plan infra change decommission-legacy-api" assistant: (invokes arn-infra-change-planner with the INFRA_CHANGE spec for resource destruction, dependency-reverse ordering, and data backup checkpoints) </example>

This agent should be used when the arn-infra-review-change skill or arn-infra-execute-change skill needs a structured quality review of completed infrastructure changes. It evaluates security posture, cost compliance, blast radius adherence, rollback documentation, environment parity, state consistency, and resource tagging. <example> Context: Post-execution review of a completed multi-phase infrastructure change user: "review infra change" assistant: (invokes arn-infra-change-reviewer with all phase reports, spec, and plan) </example> <example> Context: Mid-execution phase review gate during arn-infra-execute-change user: (automatic invocation after phase deployment and verification) assistant: (invokes arn-infra-change-reviewer with single phase report for gate check) </example> <example> Context: User wants to re-review a previously completed infrastructure change user: "re-review infra change for the migration project" assistant: (invokes arn-infra-change-reviewer with existing reports for fresh review) </example>

This agent should be used when infrastructure changes need cost estimation before deployment, when the user wants to understand the cost impact of their current or planned infrastructure, or when spend thresholds need enforcement. It integrates with Infracost when available and provides usage-based pricing estimates with clear caveats. <example> Context: Invoked by arn-infra-deploy before Level 3+ deployment operations user: "deploy to staging" assistant: (invokes arn-infra-cost-analyst to estimate cost impact before proceeding) </example> <example> Context: User asks for a cost estimate of their current infrastructure plan user: "how much will this infrastructure cost per month?" assistant: (invokes arn-infra-cost-analyst with the IaC files and provider context) </example> <example> Context: Invoked during infrastructure assessment to estimate total deployment cost user: "assess my app's infrastructure needs" assistant: (invokes arn-infra-cost-analyst with the proposed resource list) </example>

This agent should be used when the arn-infra-report skill needs diagnostic investigation of an Arness Infra workflow issue. Analyzes infrastructure configuration, directory structure, and skill behavior against expected patterns documented in the infra knowledge base. Reports only Infra-specific issues — never reads or reports user project code or business logic. <example> Context: Invoked by arn-infra-report skill during investigation phase user: "infra report" assistant: (invokes arn-infra-doctor with user description + config context) </example> <example> Context: User reports deployment failure user: "deployment to staging keeps failing with permission denied" assistant: (invokes arn-infra-doctor to check cloud CLI auth, IAM, provider config, deploy artifacts) </example> <example> Context: User reports containerization issue user: "arn-infra-containerize generated a Dockerfile that ignores my multi-stage setup" assistant: (invokes arn-infra-doctor to check Project topology, Application path, Dockerfile patterns reference) </example> <example> Context: User reports execute-change phase failure user: "execute-change failed on phase 2 and didn't create a rollback checkpoint" assistant: (invokes arn-infra-doctor to check PROGRESS_TRACKER.json, phase reports, rollback artifacts, plan structure) </example>

This agent should be used when CI/CD pipeline configurations need to be generated or extended for infrastructure deployment. It produces GitHub Actions workflows, GitLab CI configs, and other pipeline definitions. It detects existing CI/CD setups and extends them rather than replacing them. <example> Context: Invoked by arn-infra-pipeline to generate CI/CD pipeline configs user: "set up deployment pipelines" assistant: (invokes arn-infra-pipeline-builder with provider context, environment config, and existing CI detection) </example> <example> Context: User asks to add infrastructure deployment to their existing CI/CD user: "add terraform plan and apply steps to my GitHub Actions workflow" assistant: (invokes arn-infra-pipeline-builder with existing workflow files and IaC context) </example> <example> Context: Invoked to generate environment-specific pipeline stages user: "create a staging deployment pipeline" assistant: (invokes arn-infra-pipeline-builder with environment config and deployment strategy) </example>

This skill should be used when the user says "assess infrastructure", "infra assess", "arn infra assess", "infrastructure assessment", "analyze infrastructure needs", "what infrastructure do I need", "infrastructure audit", "app infrastructure assessment", "full infra assessment", "infrastructure review", "assess my app", "un-defer infrastructure", "infra backlog", or wants a comprehensive analysis of their application's infrastructure needs, including processing deferred infrastructure backlogs, to produce a prioritized infrastructure backlog published as issues.

This skill should be used when the user says "plan infra change", "arn-infra-change-plan", "infra change plan", "plan this infrastructure change", "create infra plan", "arn infra plan", "plan the infra spec", "infrastructure implementation plan", "infra plan from spec", "generate infra plan", "plan infrastructure", or wants to generate a phased implementation plan from an infrastructure change specification, structured by provisioning order, blast radius, rollback checkpoints, and environment promotion gates.

This skill should be used when the user says "infra change spec", "infrastructure change", "specify infrastructure change", "change spec", "arn infra spec", "describe infra change", "what infrastructure needs to change", "infra spec", "spec this infra change", "write infra spec", "infrastructure change specification", "create infra change spec", "upgrade to pipeline", "convert to pipeline", or wants to iteratively develop an infrastructure change idea into a well-formed specification through guided conversation, or wants to upgrade existing interactive IaC artifacts into the structured change pipeline.

This skill should be used when the user says "cleanup", "infra cleanup", "arn infra cleanup", "clean up resources", "destroy expired resources", "check ttl", "check expired", "ttl cleanup", "remove old deployments", "destroy dev environment", "tear down", "teardown infra", "destroy resources", "cleanup ephemeral", "check for expired resources", "clean up infra", "resource cleanup", "destroy old resources", "prune resources", "delete expired deployments", "decommission", or wants to check for and destroy expired ephemeral infrastructure resources. This skill also supports periodic monitoring via `/loop 6h /arn-infra-cleanup` for session-duration TTL enforcement.

This skill should be used when the user says "containerize", "dockerize", "create dockerfile", "docker setup", "container setup", "arn infra containerize", "infra containerize", "generate docker", "docker compose", "compose setup", "containerize my app", "docker configuration", "create docker-compose", "multi-stage docker", "container config", "dockerize my application", "infra docker", "set up containers", or wants to generate Dockerfiles, docker-compose configurations, and .dockerignore files for their application with security auditing and multi-stage build best practices.