This skill should be used when the user says "infra help", "arn infra help", "where am I in the pipeline", "what's next for infra", "infra status", "pipeline status", "infra pipeline", "arn-infra-help", "show infra pipeline", "what step am I on for infra", "infra workflow", "infrastructure status", "show infrastructure pipeline", or wants to see their current position in the Arness Infra workflow and get guidance on the next step. This skill detects whether the user is in Quick (interactive) mode or Full Pipeline mode and renders an ASCII diagram with the active stage marked.

This skill should be used when the user says "execute infra change", "run infra plan", "apply infrastructure change", "execute change", "arn infra execute", "deploy infra plan", "execute infrastructure plan", "run infrastructure change", "apply infra plan", "infra execute", "arn-infra-execute-change", or wants to orchestrate the phased execution of a structured infrastructure change plan, invoking agents for IaC generation, security gates, cost gates, deployment, verification, and review.

This skill should be used when the user says "manage environments", "arn infra env", "infra env", "environment setup", "configure environments", "set up staging", "set up production", "environment management", "create environment", "environment promotion", "promote to staging", "promote to production", "environment isolation", "configure dev staging prod", "environment-specific config", "tfvars per environment", "arn-infra-env", or wants to configure, create, or manage infrastructure environments (dev/staging/production) with isolation strategies, variable overrides, and promotion rules.

This skill should be used when the user says "discover tools", "infra discover", "arn infra discover", "arn-infra-discover", "audit tools", "check installed tools", "what tools do I have", "scan for MCPs", "check provider tools", "tool discovery", "discover infrastructure tools", "check my setup", "infra tooling", or wants to audit their installed infrastructure tools (MCPs, CLIs, Claude Code plugins), check authentication state, search for new official tools online, and produce a tooling manifest for the infrastructure workflow.

This skill should be used when the user says "deploy", "deploy to staging", "deploy to production", "promote to production", "infra deploy", "arn infra deploy", "deploy infrastructure", "apply infrastructure", "push to prod", "go live", "tofu apply", "terraform apply", "pulumi up", "cdk deploy", "fly deploy", "deploy to railway", "release to prod", "promote environment", or wants to execute a deployment of their infrastructure to a target environment. This skill handles environment promotion, CI/CD enforcement, cost gates, safety layers, and resource tracking.

This skill should be used when the user says "define infrastructure", "generate IaC", "infra define", "arn infra define", "generate terraform", "generate opentofu", "generate pulumi", "generate cdk", "generate bicep", "create kubernetes manifests", "provision cloud resources", "create IaC", "infrastructure as code", or wants to generate infrastructure-as-code in their chosen IaC tool for configured cloud provider(s). It produces provider-specific infrastructure code, validates it through a multi-level validation ladder, and writes an infrastructure architecture spec.

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.

This skill should be used when the user says "feature spec teams", "arness code feature spec teams", "team feature spec", "debate this feature", "collaborative feature spec", "spec with agent teams", "multi-agent feature spec", "feature spec debate", or wants to develop a feature idea through structured debate between multiple specialist agents (architects, UX experts, and security specialists) before writing the specification. Uses Claude Code's experimental Agent Teams feature. Requires Agent Teams to be enabled. For standard single-agent feature spec, use arn-code-feature-spec instead.

Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.

Write warm, direct collaboration comments. Trigger: PR feedback, issue replies, reviews, Slack messages, or GitHub comments.

Analyzes, redesigns, and automates business workflows to eliminate bottlenecks and improve efficiency. Creates process flow diagrams, identifies root-cause inefficiencies, writes standard operating procedures (SOPs), designs automation sequences, and produces implementation roadmaps with ROI estimates. Use when the user asks to map a business process, audit a workflow for inefficiencies, identify bottlenecks or handoff failures, create SOPs or checklists, design automation for repetitive tasks, apply Lean or Six Sigma techniques, or build a phased process improvement plan.

Creates structured software and platform evaluation reports with weighted scoring matrices, TCO analysis, and adoption recommendations. Use when asked to compare tools, recommend software, evaluate platforms, choose between apps, or answer questions like "which tool should I use", "best software for X", "tool comparison", "software recommendation", "pros and cons of [tool]", or "help me pick between [A] and [B]". Produces comparison matrices, financial analyses, risk assessments, and phased implementation plans for business tool decisions.

Reviews code changes, validates test coverage, checks deployment criteria, and gates production approvals based on evidence from automated screenshots, test results, and specification compliance checks. Defaults to "NEEDS WORK" unless comprehensive evidence supports readiness. Use when a user asks to approve a PR, run a release readiness check, validate deployment criteria, perform a QA gate review, check if code is production-ready, or assess integration test results.

Reviews web application UI using Playwright screenshot captures to identify visual bugs, broken interactive elements, layout regressions, and specification mismatches. Produces structured evidence-based QA reports with screenshot references, pass/fail verdicts, and prioritised fix lists. Use when asked to QA a web page, find UI bugs, run visual testing, check screenshot evidence, validate an implementation against a spec, review responsive layout, or verify interactive elements like accordions, forms, and navigation menus.

Sends HTTP requests to REST and GraphQL API endpoints, validates response codes, headers, and payloads, measures response times against SLA thresholds, generates structured test suites, and produces test reports covering functional, security, and performance scenarios. Use when the user asks about testing APIs, validating endpoints, checking HTTP status codes or response bodies, load testing, stress testing, debugging REST or GraphQL services, testing authentication flows, checking rate limiting, detecting SQL injection or OWASP API vulnerabilities, or integrating API tests into CI/CD pipelines.

Sends HTTP requests to REST and GraphQL API endpoints, validates response codes, headers, and payloads, measures response times against SLA thresholds, generates structured test suites, and produces test reports covering functional, security, and performance scenarios. Use when the user asks about testing APIs, validating endpoints, checking HTTP status codes or response bodies, load testing, stress testing, debugging REST or GraphQL services, testing authentication flows, checking rate limiting, detecting SQL injection or OWASP API vulnerabilities, or integrating API tests into CI/CD pipelines.

Filters consolidated sales data by territory, matches reports to assigned representatives, and sends personalized HTML report emails via SMTP — with full audit logging of every delivery attempt. Use when the user needs to send or schedule sales reports to reps, distribute territory-based reports, automate report delivery to a sales team, email territory data to assigned representatives, or review report distribution history. Covers daily/weekly scheduled sends, manual on-demand distribution, and querying the distribution audit trail.

Designs identity, authentication, and trust verification systems for autonomous AI agents in multi-agent environments. Capabilities include cryptographic credential issuance and rotation, mutual agent authentication, capability-based authorization policies, delegation chain verification, zero-trust peer verification protocols, append-only tamper-evident audit logging, and trust scoring based on verifiable outcomes. Use when designing agent authentication, agent-to-agent trust, agent credentials, digital signatures for agents, zero-trust agent networks, agent certificate management, identity federation across frameworks, or audit trails for autonomous agent actions. Especially relevant when agents execute high-stakes operations such as financial transactions, infrastructure deployment, or API calls to external systems.

Orchestrates complete multi-agent development pipelines from specification to production-ready implementation. Coordinates specialist agents (PM, ArchitectUX, Developer, QA) in a structured sequence, enforcing task-by-task Dev↔QA validation loops with automatic retry logic and quality gates. Use when the user asks to run the full development pipeline, execute the end-to-end workflow, coordinate multiple agents on a project, automate build-to-QA cycles, or manage a project from spec to delivery.

Collects, categorizes, and synthesizes user feedback from multiple channels into actionable product insights. Performs sentiment scoring, theme tagging, NPS/CSAT analysis, feature request ranking, priority matrix generation, and Voice of Customer reporting. Use when the user asks to analyze customer feedback, survey responses, NPS scores, CSAT data, feature requests, app reviews, support tickets, social media mentions, or any Voice of Customer data; or when they need to prioritize a product roadmap from user input, identify top pain points from feedback, understand why users are churning, or produce an executive feedback report.