/arn-brainstorming

name: arn-brainstorming
description: >-
  This skill should be used when the user says "brainstorming", "arn brainstorming",
  "brainstorm", "let's brainstorm", "start brainstorming", "brainstorming session",
  "greenfield wizard", "arn spark wizard", "greenfield pipeline",
  "walk me through greenfield", "guided greenfield", "full greenfield pipeline",
  "greenfield flow", "explore to feature backlog", "greenfield start to finish",
  "run the greenfield pipeline", "guide me through greenfield", "greenfield guided mode",
  "greenfield setup", "new project wizard", "add a feature", "new feature",
  "I need another feature", "add feature to greenfield", "one more feature",
  or wants to be walked through the entire Arness greenfield exploration pipeline
  in a single continuous session with guided decision gates instead of invoking
  each skill manually. Also triggers when the user wants to add a new feature
  to an existing greenfield project after the clickable prototype is complete.
version: 1.0.0

Arness Brainstorming

Walk the user through the entire Arness greenfield exploration 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. Conversational skills (discover, arch-vision) have internal feedback loops and flow without wizard-level gates.

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 routing, transitions between skills, progress display, and resumability.

Step 0: Ensure Configuration

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

After Step 0 completes, extract from `## Arness`:

• Vision directory, Use cases directory, Prototypes directory, Spikes directory, Visual grounding directory, Reports directory

Decision Gates

The wizard pauses at exactly 9 gates. Everything else flows automatically.

| Gate | When | Question | Options | |------|------|----------|---------| | G1 | Entry (artifacts detected) | "It looks like you have an in-progress greenfield pipeline. Resume or start fresh?" | Resume from [detected stage] / Start fresh | | G-Stress | After discover | "Run stress tests on the product concept?" then "Select which stress tests to run" | Yes/Skip; then multi-select: Interview, Competitive, Pre-Mortem, PR/FAQ | | G-Name | After stress-test/concept-review | "Explore brand names for your product?" | Yes / Skip | | G2 | After arch-vision | "Write use cases before scaffolding?" | Write use cases (recommended) / Write use cases with expert debate (teams) / Skip to scaffold | | G3 | After scaffold | "Validate technical risks before visual design?" | Run spikes (recommended if risks found) / Skip to visual sketch | | G4 | Pre-prototype | "How should prototypes be validated?" | Standard review cycles / Expert debate (teams) for both / Expert debate (teams) for clickable only | | G5 | After clickable prototype | "Lock the prototype and extract features?" | Lock prototype then extract features (recommended) / Extract features without locking / Review prototype first | | G6 | After feature extraction | "Transition to development pipeline?" | Yes, run /arn-planning / Not yet | | G7 | Entry (add-feature intent + completed prototype) | "Adding a new feature. This will update use cases, iterate the prototype, and add to the feature backlog. Ready?" | Proceed / Choose which steps to include / Cancel |

Workflow

Step 0.5: Extract Configuration

1. Read the project's CLAUDE.md `## Arness` section (guaranteed to exist after Step 0). 2. Extract configuration fields needed for artifact detection:

• **Vision directory** — for detecting product concept, architecture vision, scaffold summary, spike results, style brief, visual direction, feature backlog
• **Use cases directory** — for detecting use case files
• **Prototypes directory** — for detecting static and clickable prototype reports
• **Spikes directory** — for detecting spike POC directories
• **Visual grounding directory** — for detecting captured design references
• **Reports directory** — for detecting stress test reports and concept review report

Step 1: Detect Pipeline State (Resumability)

Check which artifacts exist on disk to determine if the user is resuming a previous pipeline run. Check from most advanced to least advanced — first match wins:

| Artifact | Detected State | Resume Point | |----------|---------------|--------------| | User says "add feature" / "new feature" AND `<prototypes-dir>/clickable/final-report.md` exists | Add Feature mode | Start at Add Feature Mode (Step AF) | | `<vision-dir>/features/feature-backlog.md` | Feature extraction complete | Resume at G6 | | `<prototypes-dir>/locked/LOCKED.md` exists AND NO `<vision-dir>/features/feature-backlog.md` | Prototype locked, extraction pending | Resume at feature-extract directly (invoke `arn-spark-feature-extract`, skip G5 lock step — already locked) | | `F-*.md` files in `<vision-dir>/features/` but NO `<vision-dir>/features/feature-backlog.md` | Feature extraction interrupted | Resume at feature-extract (invoke to complete/rebuild the Feature Tracker) | | `<prototypes-dir>/clickable/final-report.md` | Clickable prototype done | Resume at G5 | | `<prototypes-dir>/static/final-report.md` | Static prototype done | Resume at clickable prototype (Step 9b) | | `<vision-dir>/style-brief.md` | Style defined | Resume at static prototype (Step 9a) | | `<vision-dir>/visual-direction.md` | Visual direction chosen | Resume at style-explore (Step 8) | | `<vision-dir>/spike-results.md` | Spike complete | Resume at visual-sketch (Step 7) | | `<vision-dir>/scaffold-summary.md` | Scaffold built | Resume