Customize

/customize

When this runs

The user typed /corporate-legal:customize. They want to change something

in their practice profile — a risk posture, an escalation contact, a module

toggle, an output format — without re-running the whole cold-start interview

and without hand-editing YAML.

What to do

• Read the config. Read

~/.claude/plugins/config/claude-for-legal/corporate-legal/CLAUDE.md

(and ~/.claude/plugins/config/claude-for-legal/company-profile.md one

level up). If the plugin config does not exist or still contains

[PLACEHOLDER] values, say:

> You haven't run setup yet. Run /corporate-legal:cold-start-interview

> first — customize is for adjusting a profile you already have.

• Show the customizable map. List what's in the profile, grouped, with a

one-line summary of the current value:

• Company / who you are — name, industry, jurisdictions, stage, public

vs. private, practice setting *(shared across all 12 plugins — changes

flow through company-profile.md)*

• Active modules — which of M&A, Board & Secretary, Public Company,

Entity Management are on. Turning a module on/off changes which skills

prompt for setup.

• Risk posture — conservative / middle / aggressive, what each means

for diligence materiality and disclosure schedule scope

• People — deal team, board secretary, entity management owner,

escalation chain

• M&A module — materiality thresholds (contract value, headcount,

revenue), data room platforms trusted, AI bulk-review trust level

(Luminance / Kira), deal-team briefing cadence

• Board & Secretary module — house consent format, signatory

preferences, committee structure

• Public Company module — reporting calendar, disclosure controls,

10-K/10-Q review timing

• Entity Management module — entity table, registered agent, filing

jurisdictions, annual report calendar

• Workflow — matter workspaces (deal rooms), closing checklist

location, VDR watcher cadence

• Integrations — Box / Intralinks / Datasite / CT Corp / Slack status,

fallbacks

• Ask what they want to change.

> What would you like to adjust? Pick a section, or describe the change in

> your own words.

• Make the change. Show the current value, ask for the new value, explain

what changes downstream, confirm, write it to the config.

Examples:

• *Materiality threshold $250K → $500K:* "/diligence-issue-extraction

and /material-contract-schedule will now treat $500K as the cutoff.

Existing findings stay as logged; re-run if you want the new threshold

applied retroactively."

• *Turning on the Public Company module:* "I'll prompt you for reporting

calendar and disclosure controls next time you run anything in that

area."

• *AI bulk-review trust "check every row" → "spot-check 10%":* "`/ai-tool-

handoff` will QA a 10% sample rather than every extraction."

• For shared-profile changes (company name, industry, jurisdictions,

practice setting, stage): write to

~/.claude/plugins/config/claude-for-legal/company-profile.md and note:

> This change affects all 12 plugins — any plugin that reads your

> jurisdiction footprint now sees [new value].

• Close.

> Done. Your next output will reflect the change. Anything else? You can

> run /corporate-legal:customize anytime.

Guardrails

• Never delete a section. If the user wants to "remove" something, set it

to [Not configured] and explain what that means for the plugin's behavior.

• Flag internal inconsistency. If the change would make the profile

inconsistent (e.g., Public Company module off + "SEC counsel" in

escalation; or aggressive risk posture + $25K materiality threshold), flag

the tension.

• Flag guardrail degradation. The [review] flag, source attribution

tags on retrieved documents, and [verify] tags on cited authorities are

load-bearing — explain the trade-off before removing.

• One change at a time. Don't re-ask the whole interview.