/cold-start-interview

Runs the cold-start interview. First run writes ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md; subsequent runs with --redo re-interview and show a diff before overwriting.

Instructions

1. Check current state: Read ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md. If it contains [PLACEHOLDER] or [Your Company Name], proceed with fresh interview. If populated and --redo not passed, ask: "Looks like you're already set up. Want to re-run the interview? This will overwrite ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md (I'll show you a diff first)."

2. Follow the interview script below.

3. Ask for practice documents: portfolio list (or IP management export), brand guidelines, C&D template(s), enforcement playbook, OSS policy. Accept file paths, Google Drive links, or IP-management record IDs.

4. Read the shared documents and extract actual positions — enforcement thresholds, approval chain, brand watch settings, OSS rules. Note deltas between stated positions and what templates/playbooks actually require.

5. Migration: If a populated CLAUDE.md (no [PLACEHOLDER] markers) exists at ~/.claude/plugins/cache/claude-for-legal/ip-legal/*/CLAUDE.md but not at the config path, copy it to the config path and show the user what was migrated.

6. Write ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md (create parent directories as needed) per the structure below. Use the lawyer's own words where possible.

7. Seed the portfolio register if the user shared a portfolio export or IP management system access: write to ~/.claude/plugins/config/claude-for-legal/ip-legal/portfolio.yaml. If nothing was shared, leave a placeholder pointer the portfolio tracker can fill later.

8. Show summary + propose next steps:

   • "Here's what I heard — ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md is written. What did I get wrong?"
   • Offer a test: "Want to throw a proposed mark at clearance, or see what's coming up on the portfolio register?"
   • If an IP management system is connected: offer to bulk-load the portfolio register and surface upcoming renewals.

--check-integrations

Re-runs the integration availability check (IP management system, patent research, legal research, document storage, Slack) and updates ## Available integrations in ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md. Does not re-interview. Use when you connect or disconnect an MCP and want the plugin to notice without rerunning the full setup.

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.

Examples

/ip-legal:cold-start-interview

/ip-legal:cold-start-interview --redo

/ip-legal:cold-start-interview --check-integrations

Purpose

You are meeting this IP practice for the first time. Your job is to learn how they do IP work — not how IP is done in the abstract — and write what you learn into a living practice profile (the plugin config) that every other skill in this plugin reads before it does anything.

The lawyer should leave this conversation feeling like they just onboarded a sharp new paralegal who asked exactly the right questions. They should never see a YAML config file. They should see a document about their practice that they can edit in plain English.

What "cold start" means

Read ~/.claude/plugins/config/claude-for-legal/ip-legal/CLAUDE.md:

• Does not exist → start the interview.
• Contains <!-- SETUP PAUSED AT: --> → greet the user and offer to resume from that section.

…