customize
Guided customization of your litigation practice profile — change one thing without re-running the whole cold-start interview. Adjust practice role, side (plaintiff / defense / mixed), risk calibration, landscape, house style, escalation contacts, severity vocabulary, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", or "customize".
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.0w
- Forks
- 2.0k
01 前言 Front Matter
- name
- customize
- description
- Guided customization of your litigation practice profile — change one thing without re-running the whole cold-start interview. Adjust practice role, side (plaintiff / defense / mixed), risk calibration, landscape, house style, escalation contacts, severity vocabulary, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", or "customize".
- argument-hint
- [section name, or describe what you want to change]
03 SKILL.md 正文
/customize
When this runs
The user typed /litigation-legal:customize. They want to change something
in their litigation profile — a risk calibration, a house style rule, an
escalation contact, a landscape note — 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/litigation-legal/CLAUDE.md(and~/.claude/plugins/config/claude-for-legal/company-profile.mdone level up). If the plugin config does not exist or still contains[PLACEHOLDER]values, say:You haven't run setup yet. Run
/litigation-legal:cold-start-interviewfirst — 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, practice
setting (shared across all 12 plugins — changes flow through
company-profile.md) - Practice role — in-house counsel / outside counsel / solo / clinic
- Side — plaintiff / defense / mixed, and any posture nuances (class action defense, regulatory enforcement defense, commercial plaintiff, etc.)
- Risk calibration — what counts as high / medium / low risk on an inbound demand, subpoena, or new matter; escalation triggers
- Landscape — regular adversaries, friendly and unfriendly venues, judges to know, standing OC relationships
- House style — brief style, declaration format, demand letter template, deposition outline structure, legal hold template
- Severity vocabulary map — how you translate severity labels across client / internal / court-facing outputs
- People — matter leads, in-house team, outside counsel by matter type, escalation chain
- Workflow — matter workspaces, portfolio log, OC status cadence, legal hold refresh cadence
- Integrations — document storage / e-filing / calendar / Slack status, fallbacks
- Company / who you are — name, industry, jurisdictions, stage, practice
setting (shared across all 12 plugins — changes flow through
-
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:
- Side mixed → defense-only: "
/matter-intakewill stop asking the plaintiff-side questions./demand-draftwill still work for defense-side pre-suit demands but the starting frame will be different." - Risk calibration tightening high-risk threshold: "More inbound
demands and subpoenas will route through
/matter-briefingand/oc-status." - New standing OC for IP matters: "
/oc-statuswill include this firm in weekly sweeps for IP-tagged matters."
- Side mixed → defense-only: "
-
For shared-profile changes (company name, industry, jurisdictions, practice setting, stage): write to
~/.claude/plugins/config/claude-for-legal/company-profile.mdand 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
/litigation-legal:customizeanytime.
Guardrails
- Never delete a section. If the user wants to "remove" a matter type
from scope, offer to mark it
[Not currently handled]and explain what intake routing changes. - Flag internal inconsistency. If the change would make the profile inconsistent (e.g., plaintiff-only side + defense-only OC roster; or "high volume" portfolio + no matter workspaces configured), flag the tension.
- Flag guardrail degradation. The FRE 408 / privilege gate on
/demand-draft, the privilege header on matter outputs, source attribution tags, and[verify]tags on cited authorities are load- bearing — do not remove. The[review]flag and the "do not file without attorney review" framing are load-bearing. - One change at a time. Don't re-ask the whole interview.
04 同仓库更多 Skills
reg-feed-watcher
Check regulatory feeds now and report what's new since the last check, filtered by your materiality threshold. Use when the user says "check the feeds", "what's new", "regulatory update", when running from the scheduled agent, or when manually pasting a regulatory development for classification and diff.
policy-redraft
Produce a proposed marked-up policy redraft that closes a gap found by /regulatory-legal:gaps or /regulatory-legal:policy-diff. A first draft for internal review — not for direct application to approved policy documents. Use when the user says "redraft the policy", "draft the policy fix", "mark up the policy", or when gap-surfacer hands off a gap for drafting.
policy-diff
Diff a specific regulatory change against the indexed policy library. Use when a reg has changed and you need to know which policies it touches and what the gap is, when the user says "diff this reg against our policies", "which policy does this affect", or "gap analysis", or when reg-feed-watcher hands off a material item.
matter-workspace
Manage matter workspaces — create, list, switch, close, or detach the active matter (practice-level). Use when working across multiple clients or matters and you need to keep one engagement's context separate from another, or when a substantive skill needs to know which matter it's working in.
gaps
Open gaps tracker — what's flagged and not yet closed. Use when the user asks "what gaps are open", "gap tracker", "remediation status", or wants to close (--close GAP-ID) or risk-accept (--accept GAP-ID) a tracked gap.
gap-surfacer
Reference: shared gap- and comment-tracker framework backing /regulatory-legal:gaps and /regulatory-legal:comments. Tracks open policy gaps with remediation status, ingests gaps from policy-diff, surfaces what's open and aging, routes to owners, and notifies gap owners via Slack with per-send confirmation. Loaded by the gaps and comments skills before doing substantive work.