arn infra init

Other Community

Skill notes

Step 0: Existing Infrastructure Detection

Before any user interaction, scan the project for existing infrastructure artifacts. Read the local override or plugin default for existing-infra-detection.md. Scan for: IaC files: *.tf, *.hcl, Pulumi.*, cdk.json, *.bicep Container configs: Dockerfile, docker-compose.*, .dockerignore

Step 1: Check Prerequisites and Existing Configuration

Read the project's CLAUDE.md. Check for ## Arness section: If ## Arness section exists: read it and extract all fields. Note which fields are from other plugins (Plans directory, Specs directory, etc. from arn-code; Vision directory, etc. from arn-spark) -- these will be preserved when writing infra fields. If ## Arness section does NOT exist: this is a standalone infra project. A new ## Arness section will be created in Step 8.

Step 1b: Timing and Deferral

Before any configuration: Ask (using AskUserQuestion): "When do you want to set up infrastructure?" Options: Now -- Configure providers and start the infrastructure workflow

Step 2: Derive Experience Level from User Profile

Experience level governs conversational tone and recommendations throughout the init flow. Instead of asking the user directly, derive the experience level from the user profile. Read the user profile from ~/.arness/user-profile.yaml or .claude/arness-profile.local.md (project override takes precedence) If no user profile exists, run the welcome flow first by reading ${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-ensure-config/references/step-0-fast-path.md -- the welcome flow creates the profile

Step 3: Provider Configuration (Multi-Provider Aware)

Read the local override or plugin default for provider-overview.md. Read ${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-init/references/recommendation-matrix.md for expertise-adaptive recommendations. (Static reference -- not part of the evolving reference set.) Read the local override or plugin default for iac-tool-guide.md. Adapt the conversation based on experience level: Expert:

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Other
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Moderate
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Docker
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 0: Existing Infrastructure Detection

Before any user interaction, scan the project for existing infrastructure artifacts. Read the local override or plugin default for `existing-infra-detection.md`. Scan for: IaC files: `*.tf`, `*.hcl`, `Pulumi.*`, `cdk.json`, `*.bicep` Container configs: `Dockerfile`, `docker-compose.*`, `.dockerignore`

02
Step 1: Check Prerequisites and Existing Configuration

Read the project's CLAUDE.md. Check for `## Arness` section: If `## Arness` section exists: read it and extract all fields. Note which fields are from other plugins (Plans directory, Specs directory, etc. from arn-code; Vision directory, etc. from arn-spark) -- these will be preserved when writing infra fields. If `## Arness` section does NOT exist: this is a standalone infra project. A new `## Arness` section will be created in Step 8.

03
Step 1b: Timing and Deferral

Before any configuration: Ask (using `AskUserQuestion`): "When do you want to set up infrastructure?" Options: Now -- Configure providers and start the infrastructure workflow

04
Step 2: Derive Experience Level from User Profile

Experience level governs conversational tone and recommendations throughout the init flow. Instead of asking the user directly, derive the experience level from the user profile. Read the user profile from `~/.arness/user-profile.yaml` or `.claude/arness-profile.local.md` (project override takes precedence) If no user profile exists, run the welcome flow first by reading `${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-ensure-config/references/step-0-fast-path.md` -- the welcome flow creates the profile

05
Step 3: Provider Configuration (Multi-Provider Aware)

Read the local override or plugin default for `provider-overview.md`. Read `${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-init/references/recommendation-matrix.md` for expertise-adaptive recommendations. *(Static reference -- not part of the evolving reference set.)* Read the local override or plugin default for `iac-tool-guide.md`. Adapt the conversation based on experience level: Expert:

06
Step 4: Project Topology and Application Linking

Ask (using `AskUserQuestion`): "Where does your application code live?" Options: Here -- application and infrastructure are in this repository (monorepo) Separate location -- infrastructure is here, application is in another repo/folder

07
Step 5: Platform and Issue Tracker Detection

Auto-detect the infra project's own Git, Platform, and Issue tracker. This follows the same detection logic as Arness Core's `arn-code-init` Step 3 but runs independently for the infra project (in separate-repo topology, the infra repo may have different git remotes and issue trackers than the app repo). 5.1. Git check: Run `git rev-parse --is-inside-work-tree` If Git is not detected: record Git: no, Platform: none, Issue tracker: none.

08
Step 6: Environment Strategy

Ask (using `AskUserQuestion`): "How do you want to manage environments?" Options: Staging + Production (recommended) -- Changes deploy to staging first, promote to prod when ready Dev + Staging + Production -- Three-stage pipeline with a development environment

09
Step 7: Remaining Configuration

Ask: 7.1. Cost threshold: "What is your monthly infrastructure budget limit? Arness will warn before deployments that would exceed this threshold." Suggest a default based on experience level: beginner ($25), intermediate ($100), expert ($500) Accept any USD amount or "none" to disable

10
Step 7.5: Choose Model Profile for arn-infra Agents

Run the Profile selection procedure documented in `${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-ensure-config/references/step-0-fast-path.md` under the "Model profile field" section. That procedure is the single source of truth for the prompt + write + copy + checksum flow — do NOT duplicate the AskUserQuestion or file-copy logic here. The procedure performs (in order): Cross-plugin default suggestion (read sibling plugin profile fields if present in the existing `## Arness` block — e.g., if the user previously chose `balanced` for arn-code or arn-spark, suggest `balanced` here too)

11
Step 8: Create Infrastructure Files and Write Configuration

Create infrastructure directory structure: Create `.arness/infra/providers.md` with provider entries from Step 3: Create `.arness/infra/environments.md` with environment config from Step 6: Create the Arness Infra labels defined in the reference file (if Platform is github or Issue tracker is jira). Read `${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-init/references/infra-labels.md` for the full label list with colors and descriptions.

12
Step 8b: Initialize Reference Overrides

Set up locally-owned copies of the 28 evolving reference files so they survive plugin updates and can be refreshed via online research. This step creates the overrides directory, copies files from the plugin, generates SHA-256 checksums, and asks the user for their Reference updates preference. Read `${CLAUDE_PLUGIN_ROOT}/skills/arn-infra-init/references/reference-override-protocol.md` (Step 8b section) for the full initialization procedure (sub-steps 8b.1 through 8b.6).

13
Step 9: Verify and Summarize

Confirm with the user: [ ] Existing infrastructure detected and acknowledged (if any) [ ] Experience level derived from user profile: [level] [ ] Provider(s) configured: [list] [ ] Default IaC tool set: [tool]

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.