/arn-spark-use-cases-teams

name: arn-spark-use-cases-teams
description: >-
  This skill should be used when the user says "use cases teams",
  "arn use cases teams", "team use cases", "debate use cases",
  "collaborative use cases", "use cases with debate",
  "team-based use case review", "use case debate", "review use cases as a team",
  or wants to create structured use case documents through expert debate
  where product strategist and UX specialist review and discuss each other's
  findings before revising, producing a use-cases/ directory with individual
  Cockburn fully-dressed use case files and a README index.
version: 1.0.0

Arness Use Cases Teams

Create structured use case documents in Cockburn fully-dressed format through a team debate process. The `arn-spark-use-case-writer` agent drafts, then `arn-spark-product-strategist` and `arn-spark-ux-specialist` (greenfield agents in this plugin) engage in a structured debate -- reviewing each other's findings, agreeing, disagreeing, and surfacing insights neither would find alone. Supports Agent Teams for parallel debate or sequential simulation as fallback. If `arn-spark-ux-specialist` is unavailable, the skill falls back to single-reviewer mode with product strategist only. This is a conversational skill that runs in normal conversation (NOT plan mode).

This is an alternative to `arn-spark-use-cases` (independent sequential review). Use this when the project has enough complexity that expert debate adds value -- multiple actors, many use cases, or business rules that benefit from cross-disciplinary scrutiny. For simpler projects or lower token budgets, use `/arn-spark-use-cases` instead.

The primary artifacts are a **use-cases/ directory** at the project root containing individual use case files (`UC-NNN-title.md`) and a **README.md** index -- the same output format as `/arn-spark-use-cases`. Additionally, mandatory **per-round debate reports** are saved to `use-cases/reviews/`.

Prerequisites

Same prerequisites as `/arn-spark-use-cases`. Check in order:

Determine the use cases output directory: 1. Read the project's `CLAUDE.md` and check for a `## Arness` section 2. If found, extract the configured Use cases directory path — this is the source of truth 3. If no `## Arness` section exists or Arness Spark fields are missing, inform the user: "Arness Spark is not configured for this project yet. Run `/arn-brainstorming` to get started — it will set everything up automatically." Do not proceed without it. 4. If the directory does not exist, create it

> All references to `use-cases/` in this skill refer to the configured use cases directory determined above.

**Product concept (strongly recommended):** 1. Read the project's `CLAUDE.md` for a `## Arness` section. If found, look for a `Vision Directory` field and check that directory for `product-concept.md` 2. If no `## Arness` section found, check `.arness/vision/product-concept.md` at the project root

**If a product concept is found:** Use it as the primary source for actors, goals, and use case derivation.

**If no product concept is found:** Ask the user: "No product concept found. I recommend running `/arn-spark-discover` first to define your product. Alternatively, describe your application's purpose, users, and main capabilities and I will work from that."

**Architecture vision (optional):** 1. Check the same Vision directory for `architecture-vision.md` 2. If no `## Arness` section found, check `.arness/vision/architecture-vision.md` at the project root

If found: use for understanding system capabilities, constraints, and platform scope.

**Existing prototype screens (optional):** 1. Read the configured Prototypes directory from the `## Arness` section (default: `.arness/prototypes`) 2. Check for `[prototypes-dir]/clickable/` directories 3. Check for `[prototypes-dir]/static/` directories

If found: screen references can enrich use case steps with concrete screen paths.

**Style brief is NOT needed.** Use cases describe behavior, not visual presentation.

Workflow

Step 1: Detect Resume or Fresh Start

Check for existing use case output:

1. Look for `use-cases/README.md` at the project root 2. If found, scan for `use-cases/UC-*.md` files

**If existing use cases found:**

Ask (using `AskUserQuestion`):

**"I found an existing use cases directory with [N] use case files. Which would you prefer?"**

Options: 1. **Continue** — I will read the existing use cases and offer to add new ones or revise existing ones 2. **Fresh start** — I will begin from scratch (existing files will be overwritten)

If continuing: read all existing use case files and the README. Present the current catalog to the user. Ask what they want to change, add, or revise. Skip to the appropriate step.

**If no existing use cases:** Proceed to Step 2.

Step 2: Configure Debate Parameters

1. Check for Agent Teams support via Bash: `echo $CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` 2. Record the debate mode: "agent_teams" if the value is "1", otherwise "sequential". **The mode selection is based ONLY on this environment variable. File-based review output works identically in both modes and does NOT affect mode selection. When Agent Teams is enabled, always use Agent Teams mode.** 3. Check `arn-spark-ux-specialist` availability by attempting to invoke it with a minimal prompt (e.g., "Respond with OK to confirm availability"). If the agent is not found or the invocation fails, record single-reviewer mode.

Present the configuration:

"**Debate configuration:**

• **Debate mode:** [Agent Teams (parallel debate) / Sequential (simulated debate)]
• **Reviewers:** arn-spark-product-strategist + arn-spark-ux-specialist [/ arn-spark-product-strategist only (UX specialist unavailable)]
• **Max review rounds:** 2 (each round: expert debate + writer revision)

Ask (using `AskUserQuestion`):

**"Confirm debate configuration or adjust?"**

Options: 1. **Confirm** — Proceed with these settings 2. **Adjust** — Change max review