/arn-infra-wizard

name: arn-infra-wizard
description: >-
  This skill should be used when the user says "infra wizard", "arn infra wizard",
  "guided infra", "walk me through infrastructure", "infrastructure pipeline",
  "full infra pipeline", "infra flow", "run the infra pipeline",
  "guide me through infrastructure", "infra guided mode", "infrastructure wizard",
  "end to end infrastructure", "deploy everything", "set up my infrastructure",
  "infra start to finish", "arn infra guided", "run infra wizard",
  "set up everything", "complete infra setup",
  or wants to be walked through the entire Arness infrastructure pipeline in a
  single continuous session with guided decision gates instead of invoking each
  skill manually.
version: 1.0.0

Arness Infra Wizard

Walk the user through the entire Arness infrastructure pipeline in a single continuous session. The wizard invokes each pipeline skill in sequence using the Skill tool, only pausing at genuine decision gates where user input is needed.

This skill is a **sequencer and decision-gate handler**. It MUST NOT duplicate sub-skill logic. All pipeline work is done by the invoked skills. The wizard handles: entry mode detection, transitions between skills, progress display, expertise-adaptive step selection, and artifact-based resumability.

Step 0: Ensure Configuration

Read `${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-ensure-config/references/step-0-fast-path.md` and follow its instructions. This guarantees a user profile exists and `## Arness` is configured with Arness Infra fields before proceeding.

After Step 0 completes, read `${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-ensure-config/references/experience-derivation.md` and derive the user's infrastructure experience level from their profile.

Arness Core is optional but enhances cross-plugin workflows when present. If a `## Arness` section exists with Arness Core fields (plans directory, specs directory, etc.), note the configuration for cross-plugin context. This information may be useful for linking infrastructure changes to application features, but is NOT required.

Extract all `## Arness` config fields for use throughout the wizard:

• **Experience level** -- derived from user profile (see experience-derivation.md). If no profile exists, check for legacy `Experience level` in `## Arness` as fallback.
• **Deferred** -- triggers assessment-driven entry mode
• **Providers config** -- path to `providers.md`
• **Environments config** -- path to `environments.md`
• **Tooling manifest** -- path to `tooling-manifest.json`
• **Resource manifest** -- path to `active-resources.json`
• **Default IaC tool** -- for artifact detection
• **Project topology** -- for context
• **CI/CD platform** -- for CI/CD context (github-actions, gitlab-ci, bitbucket-pipelines, none)
• **Issue tracker** -- for triage entry mode detection

Mode Selection

After prerequisites, present the user with a mode choice. This determines which pipeline flow the wizard uses for the entire session.

Ask (using `AskUserQuestion`):

**"What type of infrastructure change are you making?"**

Options: 1. **Quick mode** -- Simple, low-risk changes to a single environment. Uses the interactive flow: discover, define, deploy, verify. No planning overhead. 2. **Full pipeline mode** -- Complex, multi-environment, or compliance-sensitive changes. Uses the structured flow: change-spec, change-plan, save-plan, execute-change, review-change, document-change. Includes review gates, cost tracking, and audit trails.

**Mode recommendation logic:**

Analyze the user's change description (if provided) or project context to recommend a mode:

• Single environment + single resource type + low blast radius --> recommend **Quick mode**
• Multi-environment + multiple resources + compliance requirements --> recommend **Full Pipeline mode**
• Existing pipeline artifacts in `.arness/infra-specs/` or `.arness/infra-plans/` --> recommend **Full Pipeline mode** (resume)
• No change description provided --> present both options without recommendation

If the user does not specify, default to Quick mode for beginner experience level and present both options for intermediate/expert.

---

Entry Mode Detection

After mode selection, detect the appropriate entry mode within the selected mode. Each mode has a set of entry modes checked from most specific to least specific -- first match wins.

**Quick mode entry modes:** Fresh/Resume (default), Triage-driven, Assessment-driven, Migration. **Full Pipeline entry modes:** Change Pipeline (resume or explicit), New Pipeline (default).

> Read `${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-wizard/references/entry-modes.md` for the complete entry mode detection rules, conditions, and pipeline sequences.

The workflow steps below (Step 1a, Step 1b) correspond to Entry Mode 2 (Triage-Driven) and Entry Mode 3 (Assessment-Driven) respectively.

---

Full Pipeline Mode Flow

> Read ${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-wizard/references/full-pipeline-flow.md

---

Expertise-Adaptive Pipeline

Expert / Intermediate

Full 10-step pipeline with 8 decision gates (Q1, Q1.5, Q2 through Q7). All steps are presented. Decision gates allow skipping optional steps.

Beginner

Simplified 6-step pipeline focusing on the essentials: 1. init (already done) 2. discover 3. containerize 4. define 5. deploy 6. verify

Advanced steps (pipeline, env, secrets, monitor) are offered as optional extras after the core pipeline completes:

"The core infrastructure is deployed and verified. These additional steps are optional but recommended for production readiness:

• **CI/CD Pipeline** -- Automate future deployments
• **Environment Management** -- Set up staging/prod promotion
• **Secrets Management** -- Secure your credentials
• **Monitoring** -- Set up health checks and alerting

Ask (using `AskUserQuestion`):

**"Would you like to set up any of these optional features?"**

Options: 1. **All** -- Set up all optional features 2. **Pick indivi