# Cold Start Interview

Run the cold-start interview, learns your AI governance practice and writes...

- Repository: https://github.com/anthropics/claude-for-legal (9865 stars)
- Category: AI and agents
- License: Apache-2.0
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add anthropics/claude-for-legal --skill cold-start-interview -g -a claude-code -y`
Codex: `npx skills add anthropics/claude-for-legal --skill cold-start-interview -g -a codex -y`
Cursor: `npx skills add anthropics/claude-for-legal --skill cold-start-interview -g -a cursor -y`
Gemini CLI: `npx skills add anthropics/claude-for-legal --skill cold-start-interview -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add anthropics/claude-for-legal`

## 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".

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# /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

The rest: https://github.com/anthropics/claude-for-legal/blob/HEAD/ai-governance-legal/skills/cold-start-interview/SKILL.md