From arn-infra
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.
npx claudepluginhub appsvortex/arness --plugin arn-infraThis skill uses the workspace's default tool permissions.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Builds 3-5 year financial models for startups with cohort revenue projections, cost structures, cash flow, headcount plans, burn rate, runway, and scenario analysis.
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.
Read ${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-ensure-config/references/ensure-config.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 in ## Arness as fallback.providers.mdenvironments.mdtooling-manifest.jsonactive-resources.jsonAfter 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:
Mode recommendation logic:
Analyze the user's change description (if provided) or project context to recommend a mode:
.arness/infra-specs/ or .arness/infra-plans/ --> recommend Full Pipeline mode (resume)If the user does not specify, default to Quick mode for beginner experience level and present both options for intermediate/expert.
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.mdfor 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.
Read ${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-wizard/references/full-pipeline-flow.md
Full 10-step pipeline with 8 decision gates (Q1, Q1.5, Q2 through Q7). All steps are presented. Decision gates allow skipping optional steps.
Simplified 6-step pipeline focusing on the essentials:
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:
Ask (using AskUserQuestion):
"Would you like to set up any of these optional features?"
Options:
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:
Skill: arn-infra:arn-infra-change-spec with the existing artifacts as input context:
Proactive upgrade detection:
After any Quick mode step completes, check if the change complexity warrants an upgrade. Offer an upgrade if:
arn-infra-define interactively and the generated IaC touches multiple environments or providersProactive 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.
Read ${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-wizard/references/decision-gates.md
Read ${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-wizard/references/artifact-detection.md
## Arness config fields. If ## Arness section exists, note it for cross-plugin context.If artifacts detected (Fresh/Resume mode only):
Show the detected state and ask Q1:
"It looks like you have an in-progress infrastructure pipeline at [detected stage]. Would you like to resume from there, or start fresh?"
If no artifacts detected: skip Q1 and proceed to Step 2.
This step runs only when Entry Mode 2 (Triage-Driven) was detected in Step 0.
Inform the user: "Processing [N] pending infrastructure request(s)..."
Skill: arn-infra:arn-infra-triage
When triage completes, the implications brief is available. Proceed directly to Step 4 (Define) — skip discover and containerize since the triage brief already contains the analyzed requirements.
This step runs only when Entry Mode 3 (Assessment-Driven) was detected in Step 0.
Inform the user: "Running full infrastructure assessment on deferred backlog..."
Skill: arn-infra:arn-infra-assess
When assess completes, the user has a prioritized infrastructure backlog. Proceed directly to Step 4 (Define) — skip discover and containerize since the assessment has already produced the infrastructure plan.
Show progress (Expert/Intermediate):
Infra Pipeline: DISCOVER --> containerize --> define --> deploy --> verify --> pipeline --> env --> secrets --> monitor
^^^^^^^^
Show progress (Beginner):
Infra Pipeline: DISCOVER --> containerize --> define --> deploy --> verify
^^^^^^^^
Inform the user: "Auditing your installed tools, MCPs, and CLIs..."
Skill: arn-infra:arn-infra-discover
When discover completes, tooling-manifest.json exists at the Tooling manifest path.
After discover, check the tooling manifest for tools with "status": "recommended" and "installed": false.
If missing recommended tools are found, present Q1.5. Otherwise, skip to Step 3.
Show progress:
Infra Pipeline: discover --> CONTAINERIZE --> define --> deploy --> verify --> pipeline --> env --> secrets --> monitor
^^^^^^^^^^^^
Ask Q2 (see Decision Gates section).
If Yes:
Skill: arn-infra:arn-infra-containerize
If Skip: mark containerize as skipped and proceed to Step 4.
Show progress:
Infra Pipeline: discover --> containerize --> DEFINE --> deploy --> verify --> pipeline --> env --> secrets --> monitor
^^^^^^
Inform the user: "Generating infrastructure-as-code configurations..."
Skill: arn-infra:arn-infra-define
When define completes, IaC configuration files exist in the project.
Show progress:
Infra Pipeline: discover --> containerize --> define --> DEPLOY --> verify --> pipeline --> env --> secrets --> monitor
^^^^^^
Ask Q3 (see Decision Gates section).
Based on user choice:
Skill: arn-infra:arn-infra-deploy (pass the target environment as context)Skill: arn-infra:arn-infra-deploy (pass dry-run mode as context)Show progress:
Infra Pipeline: discover --> containerize --> define --> deploy --> VERIFY --> PIPELINE --> env --> secrets --> monitor
^^^^^^ ^^^^^^^^
Ask Q4 (see Decision Gates section).
Based on user choice:
Verify then CI/CD:
Skill: arn-infra:arn-infra-verifyThen:Skill: arn-infra:arn-infra-pipeline
Verify only:
Skill: arn-infra:arn-infra-verify
CI/CD only:
Skill: arn-infra:arn-infra-pipeline
Skip both: proceed to Step 7
Beginner: Skip to Step 8 (beginner optional extras prompt).
Show progress:
Infra Pipeline: discover --> containerize --> define --> deploy --> verify --> pipeline --> ENV --> secrets --> monitor
^^^
Ask Q5 (see Decision Gates section).
If Yes:
Skill: arn-infra:arn-infra-env
If Skip: proceed to Step 8.
Beginner: Present the optional extras prompt (see Expertise-Adaptive Pipeline section). If the user selects specific extras, invoke the corresponding skills. Otherwise, skip to Step 9.
Show progress:
Infra Pipeline: discover --> containerize --> define --> deploy --> verify --> pipeline --> env --> SECRETS --> MONITOR
^^^^^^^ ^^^^^^^
Ask Q6 (see Decision Gates section).
Based on user choice:
Both:
Skill: arn-infra:arn-infra-secretsThen:Skill: arn-infra:arn-infra-monitor
Secrets only:
Skill: arn-infra:arn-infra-secrets
Monitoring only:
Skill: arn-infra:arn-infra-monitor
Skip both: proceed to Step 9
Show final progress (Expert/Intermediate):
Infra Pipeline: discover --> containerize --> define --> deploy --> verify --> pipeline --> env --> secrets --> monitor
✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
Show final progress (Beginner):
Infra Pipeline: discover --> containerize --> define --> deploy --> verify
✓ ✓ ✓ ✓ ✓
Use ✓ for completed steps, skipped for skipped steps, and · for steps not reached.
Present a completion summary:
[tooling-manifest-path] (completed / skipped)Next steps:
/arn-infra-wizard again to revisit any step (artifact detection will resume where appropriate)"/arn-infra-deploy to deploy to additional environments"/arn-infra-migrate to migrate between providers"/arn-infra-triage to process remaining infrastructure requests"AskUserQuestion): "The [skill-name] step encountered an error: [error summary]. What would you like to do?" Options: retry this step / skip this step / abort the wizard. If retry, re-invoke the same skill. If skip, continue to the next gate. If abort, show what was completed and exit./arn-infra-wizard again to resume (artifact detection will pick up where you left off)."## Arness): Continue without Arness Core context. Cross-plugin features (linking to application specs/plans) will be unavailable. Optionally inform: "Arness Code is not configured. The wizard will operate in standalone mode. Install and configure the Arness Code plugin for cross-plugin features."## Arness missing): Step 0 (ensure-config) handles this automatically. If ensure-config itself fails, inform the user and suggest running /arn-infra-wizard again..arness/infra-specs/ contains multiple INFRA_CHANGE_*.md files, list them and ask the user which change to resume. Do not guess.Skill: arn-infra:arn-infra-<name>.