/arn-spark-init

name: arn-spark-init
description: >-
  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.
version: 1.0.0

Arness Spark Init

Set up Arness for a greenfield project by configuring output directories for all greenfield artifacts and detecting the project's platform setup. This is optional — Arness Spark auto-configures with sensible defaults on first skill invocation. Use this to customize directories, add design tool integrations (Figma, Canva), or review your current settings.

This skill is lightweight and focused: it configures only what greenfield skills need (artifact directories and platform integration). It does NOT set up code patterns, report templates, plans, or documentation directories — those are handled when the project transitions to the development phase. Design tool integration (Figma/Canva) is only available through this skill — ensure-config does not configure design tools.

The `## Arness` section written by this skill is forward-compatible with Arness Code and Arness Infra. When either plugin's ensure-config or init runs later, it detects the existing configuration and adds the remaining fields without disrupting greenfield settings.

Workflow

Step 1: Check Existing Configuration

Read the project's CLAUDE.md and look for a `## Arness` section. If no CLAUDE.md exists, create one at the project root before proceeding.

**If the section does not exist:**

• Proceed to Step 2 (fresh init)

**If the section exists:** 1. Parse all config fields from the existing `## Arness` block 2. Read the current plugin version from `${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json` 3. Show the user their current configuration 4. Ask via `AskUserQuestion`:

• **Review** — Show current configuration summary, no changes
• **Update** — Check for missing greenfield fields and fill them in
• **Reconfigure** — Re-run the full setup flow from scratch
• **Keep** — No changes
• If **Review** → display a clean summary of all `## Arness` fields relevant to Arness Spark, then exit the skill
• If **Keep** → done, exit the skill
• If **Reconfigure** → continue to Step 2, pre-filling known values as defaults
• If **Update** → check which greenfield fields are missing (Vision directory, Use cases directory, Prototypes directory, Spikes directory, Visual grounding directory, Reports directory, Git, Platform, Issue tracker, Figma, Canva) and only process those. For missing directory fields, ask the user with the existing value as the default. For missing Git/Platform/Issue tracker, re-run Step 3 detection. For missing Figma/Canva, re-run Step 3.4 design tool integration. Then proceed to Step 4 to write the updated config. Preserve all existing fields that are not managed by this skill (such as Plans directory, Specs directory, Report templates, etc.).

---

Step 2: Configure Output Directories

Ask the user about each output directory. All defaults are under `.arness/` to centralize Arness artifacts in one place.

**2.1. Vision directory:**

"Where should Arness store greenfield vision documents (product concept, architecture vision, style brief, spike results, feature backlog)?"

• Default: `.arness/vision`
• Used by: `/arn-spark-discover`, `/arn-spark-arch-vision`, `/arn-spark-spike`, `/arn-spark-style-explore`, `/arn-spark-feature-extract`, `/arn-spark-dev-setup`

**2.2. Use cases directory:**

"Where should Arness store use case documents?"

• Default: `.arness/use-cases`
• Used by: `/arn-spark-use-cases`, `/arn-spark-use-cases-teams`

**2.3. Prototypes directory:**

"Where should Arness store prototype versions and review reports?"

• Default: `.arness/prototypes`
• Used by: `/arn-spark-static-prototype`, `/arn-spark-clickable-prototype`

**2.4. Spikes directory:**

"Where should Arness store technical spike POC code?"

• Default: `.arness/spikes`
• Used by: `/arn-spark-spike`

**2.5. Visual grounding directory:**

"Where should Arness store visual grounding assets (reference images, design mockups, brand assets)?"

• Default: `.arness/visual-grounding`
• Used by: `/arn-spark-style-explore`, `/arn-spark-static-prototype`, `/arn-spark-clickable-prototype`

Create three subfolders inside the visual grounding directory: `references/`, `designs/`, `brand/`.

**2.6. Reports directory:**

"Where should Arness store stress test reports and other analysis output?"

• Default: `.arness/reports`
• Used by: `/arn-spark-stress-interview`, `/arn-spark-stress-competitive`, `/arn-spark-stress-premortem`, `/arn-spark-stress-prfaq`, `/arn-spark-concept-review`

After creating the Reports directory (`mkdir -p <chosen-path>`), also create the `stress-tests/` subdirectory: `mkdir -p <chosen-path>/stress-tests/`

For each directory:

• Accept any relative path the user provides (relative to the project root)
• If updating an existing config (from Step 1), show the current path as the default
• Create the directory if it does not exist: `mkdir -p <chosen-path>`

---

Step 3: Detect Git, Platform, and Issue Tracker

**Shared field preservation:** If `## Arness` already exists and the shared fields (Git, Platform, Issue tracker, Jira site, Jira project) are already present from a prior init (this plugin or another — e.g., arn-code-init or arn-infr