arness

arn-infra-define

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.

arn-spark-prototype-lock

This skill should be used when the user says "prototype lock", "lock prototype", "arn prototype lock", "freeze prototype", "preserve prototype", "snapshot prototype", "protect prototype", "archive prototype", "save the prototype", "don't overwrite the prototype", "lock the design", "freeze the design", or wants to create a frozen snapshot of the validated prototype before development begins, preventing production code from overwriting the validated reference artifact.

arn-infra-change-plan

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.

arn-infra-review-change

This skill should be used when the user says "review infra change", "infrastructure review", "review infrastructure", "infra quality review", "arn infra review", "check infra change", "review infrastructure change", "infra change review", "quality check infrastructure", "arn-infra-review-change", "post-deployment review", or wants to perform a comprehensive post-execution quality review of completed infrastructure changes, producing a structured review report with a PASS/WARN/NEEDS_FIXES verdict.

arn-spark-style-explore

This skill should be used when the user says "style explore", "arn style", "visual style", "explore styles", "UI style", "look and feel", "design direction", "pick a style", "choose colors", "theme the app", "visual direction", "style guide", or wants to explore and define the visual design direction for their project through guided conversation, producing a style brief document with implementable toolkit configuration.

arn-spark-stress-premortem

This skill should be used when the user says "pre-mortem", "premortem", "risk analysis", "stress premortem", "failure analysis", "what could go wrong", "pre mortem", "investigate failure", "failure modes", or wants to stress-test a product concept by applying Gary Klein's pre-mortem methodology to identify hypothetical failure root causes, early warning signals, and mitigation strategies. Produces a pre-mortem report with 3 root causes across distinct failure dimensions and recommended concept updates.

arn-code-feature-spec-teams

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.

arn-shipping

This skill should be used when the user says "shipping", "arness shipping", "ship it", "ship", "create PR", "open pull request", "push and PR", "commit and push", "wrap up", "ship the feature", "ship the fix", "ready to ship", "push changes", "finalize", "finish up", "done", "arn-shipping", or wants to commit, push, and optionally create a pull request. Handles branching, staging, committing, pushing, and PR creation as a single guided flow. Chains from arn-implementing at completion.

arn-spark-arch-vision

This skill should be used when the user says "arch vision", "architecture vision", "arn arch vision", "define the architecture", "tech stack", "what technology should I use", "design the system", "system architecture", "how should I build this", "technology choices", "choose technologies", "pick a tech stack", or wants to explore technology options and define the high-level architecture for a greenfield project. Takes a product concept as input and produces an architecture-vision.md document capturing the technology stack, system design, protocols, packaging strategy, and known risks.

arn-infra-pipeline

This skill should be used when the user says "infra pipeline", "arn infra pipeline", "create CI/CD pipeline", "set up deployment pipeline", "generate pipeline", "infra CI/CD", "deployment pipeline", "setup cicd", "generate github actions", "generate gitlab ci", "generate bitbucket pipeline", "infrastructure pipeline", "pipeline setup", "create deployment workflow", "cicd for infrastructure", "infra deployment pipeline", "set up infrastructure CI/CD", "arn-infra-pipeline", or wants to generate infrastructure-specific CI/CD pipelines with SOC 2 alignment, OIDC authentication, and environment-aware deployment stages.

arn-spark-visual-readiness

This skill should be used when the user says "visual readiness", "check visual layers", "activate visual layer", "visual checkpoint", "promote visual testing", "enable layer 2", "visual test health", "check deferred layers", "activate deferred layers", "layer promotion", or wants to validate and activate deferred visual testing layers after project milestones.

arn-code-swift

This skill should be used when the user says "swift", "arness code swift", "quick change", "small change", "just do this", "quick feature", "quick implementation", "swift fix", "implement this quickly", "add this quickly", "simple change", "just implement this", "arn-code-swift", "swift mode", "quick task", or wants a lightweight, pattern-aware implementation for a small feature or enhancement (1-8 files) without going through the full Arness pipeline. Bridges the gap between raw Claude Code and the full feature-spec/plan pipeline. Includes architectural assessment, targeted testing, and pattern compliance review.

arn-spark-init

Optional customization tool for greenfield projects. This skill should be used when the user says "greenfield init", "arn spark init", "initialize greenfield", "setup greenfield", "greenfield setup", "start greenfield", "configure greenfield", "set up greenfield", "init greenfield", "greenfield configuration", "review greenfield config", "customize greenfield config", "greenfield settings", "Figma setup", "Canva setup", "add Figma", "add Canva", "design tool setup", or wants to customize Arness Spark configuration, add design tool integrations (Figma, Canva), or review current greenfield settings. Arness Spark auto-configures with sensible defaults on first skill invocation — this init is optional. Design tool integration (Figma/Canva) remains available only through this skill.

arn-code-plan

This skill should be used when the user says "arness code plan", "arn-code-plan", "plan this", "write a plan", "create plan", "implementation plan", "plan feature", "plan the spec", "plan from spec", "generate plan", "arness code plan FEATURE_X", "plan the bugfix", "plan bugfix", "make a plan", or wants to generate an implementation plan from a Arness specification. The skill invokes the arn-code-feature-planner agent to generate the plan, presents it for review, and iterates on user feedback until approved. Produces a PLAN_PREVIEW file that feeds into /arn-code-save-plan.

arn-code-execute-plan

This skill should be used when the user says "execute plan", "run the plan", "start execution", "execute project", "execute all tasks", "run all tasks", "run plan in parallel", "execute with review gates", or wants to execute a full structured project plan after tasks have been created via arn-code-taskify. This skill runs ALL tasks from the task list — for executing a single specific task, use arn-code-execute-task instead. For Agent Teams mode, use arn-code-execute-plan-teams. Do NOT use this skill when executing a single task — use `/arn-code-execute-task` instead.

arn-spark-clickable-prototype

This skill should be used when the user says "clickable prototype", "arn clickable prototype", "interactive prototype", "test interactions", "validate UX", "user journeys", "test navigation", "make it clickable", "prototype interactions", "test the prototype", "build the screens", "create the UI", "screen mockups", or wants to generate a clickable interactive prototype with linked screens and validate it through iterative build-review cycles with Playwright-based interaction testing, per-criterion scoring, an independent judge verdict, and versioned output.

arn-code-batch-simplify

This skill should be used when the user says "batch simplify", "cross-feature simplify", "batch simplification", "simplify all features", "cross-feature quality pass", "batch code cleanup", "consolidate across features", "deduplicate across features", "cleanup after batch merge", "cross-feature deduplication", "arness batch simplify", "arn-code-batch-simplify", "simplify merged features", "post-merge simplify", "find cross-feature duplication", or wants to run a post-merge quality pass that finds duplication and consolidation opportunities across independently implemented features. This requires merged features in .arness/plans/ — run arn-code-batch-merge first if none are merged.

arn-code-review-pr

This skill should be used when the user says "review PR", "review pull request", "check PR comments", "review PR feedback", "review PR 123", "analyze PR comments", "validate PR review", "address PR feedback", "fix PR issues", "what did the reviewer say", "review Bitbucket PR", or wants to validate GitHub or Bitbucket PR review comments, categorize findings, and optionally connect back into the Arness pipeline for fixes. Do NOT use this for creating PRs (use arn-code-ship) or reviewing implementation quality (use arn-code-review-implementation).

arn-infra-triage

This skill should be used when the user says "triage infra request", "infra triage", "arn infra triage", "process infra issue", "handle infra request", "infrastructure request", "triage infrastructure", "analyze infra issue", "infra request analysis", "process infrastructure request", or wants to process an incoming infrastructure request issue created by Arness Core or manually, analyze its infrastructure implications, and produce a structured implications brief.

arn-infra-verify

This skill should be used when the user says "verify deployment", "verify infra", "check deployment", "arn infra verify", "infra verify", "health check", "check health", "verify staging", "verify production", "is my deployment healthy", "check if deployment worked", "run health checks", "deployment verification", "check infrastructure", "validate deployment", "verify environment", "post-deployment check", "infra health", "check dns", "check ssl", "verify endpoints", "smoke test", "integration test", or wants to validate that a deployed environment is healthy and its resources match the expected state. This skill runs health checks, DNS verification, SSL validation, resource state comparison, and updates issue labels and environments.md with verification results.

arn-spark-ensure-config

This skill should be used when the user says "ensure config", "check arn spark config", "arn-spark-ensure-config", "verify arn spark setup", "configure spark", "setup arness spark", "spark config", or wants to verify that Arness Spark configuration is present for the current project. This skill is primarily consumed as a reference by entry-point skills (arn-brainstorming, arn-spark-discover, arn-spark-arch-vision) which read the ensure-config reference as Step 0 before proceeding with their workflow.

arn-infra-assess

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.

arn-code-taskify

This skill should be used when the user says "taskify", "create task list", "create tasks", "convert plan to tasks", "generate tasks from plan", "create tasks from plan", "turn plan into tasks", "arness code taskify", or wants to convert a structured project plan's TASKS.md into an executable Claude Code task list with proper dependency management.

arn-infra-env

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.

arn-infra-cleanup

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.