/cold-start-interview

name: cold-start-interview
description: >
  Run the cold-start interview — learns your AI governance practice and writes
  `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md` from
  your AI policy, a reference impact assessment, and key vendor AI agreements.
  Use when the practice profile is missing or contains `[PLACEHOLDER]` markers,
  or when user says "set up ai governance plugin", "onboard me", "configure ai
  governance".
argument-hint: "[--redo | --check-integrations]"

/cold-start-interview

1. Check `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md` — if populated and no `--redo`, confirm before overwriting. 2. Run the interview using the workflow below (includes Part 0 role + integration check). 3. Seed docs: AI/acceptable use policy (URL or file), a prior impact assessment, key vendor AI agreements, model inventory or allowlist/blocklist if they exist. Read all provided. 4. Extract: policy commitments and prohibitions, vendor positions (note gaps vs. stated), impact assessment structure, approved/prohibited tool lists. 5. Migration: if a populated CLAUDE.md (no `[PLACEHOLDER]` markers) exists at `~/.claude/plugins/cache/claude-for-legal/ai-governance-legal/*/CLAUDE.md` but not at the config path, copy it to the config path and tell the user what was migrated. 6. Write `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md` (create parent directories as needed). Show summary. Offer first task.

Flags

• `--redo` — re-run the full interview and overwrite `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md`.
• `--check-integrations` — re-scan available MCP connectors and refresh the `## Available integrations` table in `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md` without re-running the full interview. Use after setting up a new connector (Slack, document storage, scheduled-tasks).

When probing: only report ✓ if an MCP tool call actually succeeded. Configured-but-untested connectors should be marked ⚪ with a one-line how-to for confirming. Never report ✓ based on `.mcp.json` declarations alone — that misleads users into thinking something is wired up when it isn't.

/ai-governance-legal:cold-start-interview
/ai-governance-legal:cold-start-interview --check-integrations

---

Purpose

Learn how *this* AI governance team works — what role the company plays in the AI supply chain, which regulations actually apply to them, what their red lines are for AI use cases, and what good impact assessment looks like here. Write it into the plugin config so every other skill reads from the same understanding.

AI governance postures vary enormously. A company that builds AI products for enterprise customers has almost nothing in common with a company that deploys off-the-shelf AI tools internally. The interview figures out which one this is before anything else — because builder obligations and deployer obligations are nearly opposite exercises.

Cold-start check

Read `~/.claude/plugins/config/claude-for-legal/ai-governance-legal/CLAUDE.md`:

• **Does not exist** → start the interview.
• **Contains `<!-- SETUP PAUSED AT: -->`** → greet the user and offer to resume from that section.
• **Contains `[PLACEHOLDER]` markers but no pause comment** → the template was never completed; offer to start fresh or resume from wherever the placeholders begin.
• **Populated (no placeholders, no pause comment)** → already configured; skip unless `--redo`.

The template structure lives at `${CLAUDE_PLUGIN_ROOT}/CLAUDE.md` — use it as the section scaffold. Write the completed practice profile to the config path, creating parent directories as needed.

If a CLAUDE.md exists at the old cache path `~/.claude/plugins/cache/claude-for-legal/ai-governance-legal/*/CLAUDE.md` but not at the config path, copy it forward to the config path before proceeding.

Check for the shared company profile

Look for `~/.claude/plugins/config/claude-for-legal/company-profile.md`.

• **If it exists:** Read it. Show a one-line confirmation: "You're [name], [practice setting], at [company], [industry], operating in [jurisdictions]. Right? (Or say 'update' to change the shared profile.)" If confirmed, skip the company questions — go straight to the plugin-specific ones.
• **If it doesn't exist:** You'll be the first plugin this user set up. After the orientation and fork, ask the company questions and write them to the shared profile (per the template at `references/company-profile-template.md` in the plugin root), then continue with the plugin-specific questions. Tell the user: "I've saved your company profile — the other legal plugins will read it and skip these questions."

The company questions that belong in the shared profile (and should NOT be re-asked if it exists): practice setting, company name, industry, what-you-sell, size, jurisdictions, regulators, risk appetite, escalation names. The plugin-specific questions (playbook positions, review framework, house style, supervision model, etc.) stay per-plugin.

Install scope check

Before the orientation, if you notice the working directory is inside a project (not the user's home directory), flag it. Say once:

> **Heads up — it looks like this plugin may be project-scoped, which means I can only read files in [current directory]. If you'll want me to read documents from elsewhere (Downloads, Documents, Dropbox), install user-scoped instead — see QUICKSTART.md. You can continue with project scope, but you'll need to move files into this folder.**

Ask the user to confirm before proceeding: continue with project scope, or pause to reinstall user-scoped. If the working directory *is* the user's home directory, skip this check silently.

Before the interview starts

Open with the fork-first preamble. Keep it to 3-4 short lines. Ask quick-or-full before anything else.

> **`ai-governance-legal` is for people who run AI governance: use-ca