arn-infra-wizard

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 individually -- Choose which features to set up
3. Skip -- Skip all optional features

Interactive-to-Pipeline Upgrade Path

At any point during Quick mode, the user may request an upgrade to Full Pipeline mode. Detect upgrade requests when the user says any of: "I want review gates", "upgrade to pipeline", "add audit trail", "switch to full pipeline", "need more structure", or "this is getting complex".

Upgrade flow:

1. Acknowledge the upgrade request: "Upgrading to Full Pipeline mode. I will create a structured change specification from your existing progress."
2. Invoke Skill: arn-infra:arn-infra-change-spec with the existing artifacts as input context:
3. Pass any IaC files generated by define
4. Pass any deployment results from deploy
5. Pass any verification results from verify
6. Pass the tooling manifest from discover
7. When change-spec completes, continue in Full Pipeline mode from P2 (change-plan) onward.

Proactive upgrade detection:

After any Quick mode step completes, check if the change complexity warrants an upgrade. Offer an upgrade if:

• The user has run arn-infra-define interactively and the generated IaC touches multiple environments or providers
• The deployment scope has expanded beyond the initial single-environment expectation
• The user mentions compliance, audit, or review requirements

Proactive offer: "I see you have generated IaC code that spans multiple environments. Would you like to wrap this in the structured pipeline for review gates and documentation? (yes / no)"

If the user accepts: follow the upgrade flow above. If the user declines: continue in Quick mode.

Decision Gates (Quick Mode)

Read ${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-wizard/references/decision-gates.md

Artifact Detection (Resumability)

Read ${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-wizard/references/artifact-detection.md

Workflow

Step 0: Initialize, Select Mode, and Detect Entry Mode

1. Read CLAUDE.md. Check prerequisites (see Prerequisites section).
2. Extract ## Arness config fields. If ## Arness section exists, note it for cross-plugin context.
3. Determine expertise level from the profile-derived experience level (see Step 0).
4. Present mode selection (see Mode Selection section). User chooses Quick or Full Pipeline.
5. If Quick mode: detect entry mode from Quick mode entry modes (see Entry Mode Detection section).
6. If Full Pipeline mode: detect entry mode from Full Pipeline mode entry modes (see Entry Mode Detection section).
7. If Quick mode Fresh/Resume: run artifact detection (see Artifact Detection section).
8. If Full Pipeline mode Change Pipeline: run pipeline artifact detection (see Entry Mode 5).

#