Customize

Codex v1 local-input note: This migrated skill supports local files and pasted text by default. References to Drive, CLM IDs, Slack, Westlaw, iManage, Ironclad, eDiscovery, dockets, or other remote systems require a separately configured Codex connector/MCP server. When a connector is unavailable, ask for a local export, local file path, or pasted excerpts. If config/local/codex-for-legal/<practice>/CLAUDE.md is missing, ask the user to run the relevant cold-start-interview or customize skill and copy from config/templates/codex-for-legal/<practice>/CLAUDE.md.

$commercial-legal:customize

When this runs

The user typed $commercial-legal:customize. They want to change something in their practice profile — a risk posture, an escalation contact, a playbook position, a jurisdiction, an output format — without re-running the whole cold-start interview and without hand-editing YAML.

What to do

1. Read the config. Read config/local/codex-for-legal/commercial-legal/CLAUDE.md (and config/local/codex-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 $commercial-legal:cold-start-interview first — customize is for adjusting a profile you already have.

2. 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, practice setting, sales-side vs. purchasing-side orientation (shared across all 12 plugins — changes flow through company-profile.md)
   • Risk posture — conservative / middle / aggressive, what each means for fallback positions and escalation triggers
   • People — escalation chain, approvers by dollar threshold and by clause type
   • Playbook positions — the substantive contract positions: liability caps, indemnity scope, IP ownership, data protection, termination, auto-renewal, price escalation, and the fallbacks for each
   • NDA triage preferences — what green / yellow / red looks like for inbound NDAs
   • Review preferences — redline style, explanation depth, whether to produce a stakeholder summary by default
   • House style — document format, signature block, renewal-alert channel, deviation-log format
   • Workflow — matter workspace paths, intake path, renewal watcher cadence
   • Integrations — Ironclad (connector optional; not enabled in v1) / DocuSign (connector optional; not enabled in v1) / Slack (connector optional; not enabled in v1) / document storage status, fallbacks

3. Ask what they want to change.

   What would you like to adjust? Pick a section, or describe the change in your own words.

4. Make the change. Show the current value, ask for the new value, explain what changes downstream, confirm, write it to the config.

   Examples:

   • Liability cap fallback 12 months → 6 months: "$commercial-legal:review will now flag anything above 6 months as a deviation; existing deal-debrief entries stay as logged."
   • New escalation approver: "Any redline exceeding your own authority will now route to this approver — /escalate will include them by default for the matching risk band."
   • Risk posture middle → aggressive: "I'll accept more vendor-friendly positions without flagging them and shift the [review] bar higher."

5. For shared-profile changes (company name, industry, jurisdictions, practice setting, stage): write to config/local/codex-for-legal/company-profile.md and note:

   This change affects all 12 plugins — any plugin that reads your jurisdiction footprint now sees [new value].

6. Close.

   Done. Your next output will reflect the change. Anything else? You can run $commercial-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., risk posture aggressive + "every redline needs GC approval"; or "sales-side" + a purchasing-side playbook position), flag the tension and ask which one they want.
• Flag guardrail degradation. If the user asks to turn off a guardrail (drop the [review] flag, skip the privilege header, remove [verify] tags), explain what the guardrail protects against and confirm they understand the trade-off. The [review] flag, source attribution tags, and [verify] tags on cited statutes are load-bearing and should not be removed.
• One change at a time. Don't re-ask the whole interview.