菜单
Update the status of an in-progress international expansion project — recalculates what is now unblocked, flags anything overdue, and surfaces the next priorities. Use when work has happened since the last session and the expansion tracker needs to reflect the current state.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | expansion-update |
| description | Update the status of an in-progress international expansion project — recalculates what is now unblocked, flags anything overdue, and surfaces the next priorities. Use when work has happened since the last session and the expansion tracker needs to reflect the current state. |
| argument-hint | [country name] |
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.mdis missing, ask the user to run the relevantcold-start-intervieworcustomizeskill and copy fromconfig/templates/codex-for-legal/<practice>/CLAUDE.md.
Returns to an open expansion tracker and updates item status based on what has happened since the last session. Recalculates what is now unblocked, flags anything overdue, and surfaces the next priorities.
Load config/local/codex-for-legal/employment-legal/CLAUDE.md.
Identify the tracker file: config/local/codex-for-legal/employment-legal/expansion-[slug].yaml. If it doesn't
exist, respond: "No expansion tracker found for [country]. Run
$employment-legal:expansion-kickoff [country] to start one."
Read the tracker. Show the current state:
[Country] Expansion — last updated [date]
Open: [N] | In progress: [N] | Done: [N] | Blocked: [N]
Next priorities (open items with earliest due dates or highest-dependency):
[item] — owner: [owner]
[item] — owner: [owner]
[item] — owner: [owner]
Ask for updates in a single prompt — do not ask about each item one by one:
Which items have moved since we last looked? Tell me what's changed (e.g., "EOR decision made — going with Deel", "outside counsel engaged — call scheduled for Thursday", "PE analysis still open, waiting on tax"). You can also add new items or change due dates.
Apply updates to the tracker file. For any item newly marked done,
check whether it unblocks other items and flag those as now actionable.
If any item has a due date that has passed and is still open or
in-progress, flag it:
⚠️ Overdue: [item] — was due [date], owner: [owner]
Tracker updated — [N] items closed, [N] still open.
Next priority: [top open item].
$employment-legal:expansion-update Germany
$employment-legal:expansion-update
(will ask which country if multiple trackers exist)
Detailed tracker schema, item-status rules, and dependency logic live in the
international-expansionreference skill — load it before doing substantive work.
EU AI Act per-system inventory — track each AI system's role (provider, deployer, importer, distributor, authorized representative, product manufacturer) and risk tier (prohibited, high-risk, limited, minimal, GPAI, GPAI+systemic). Role and tier are assessed per system, not per company. Use when the user says "ai inventory", "add an ai system", "what systems do we have", "classify this ai system", "eu ai act register", or "ai system registry".
Run an AI impact assessment — structured intake, risk analysis, regulatory classification per regime in scope, policy consistency diff, and recommendation with conditions. Uses the house-style structure learned from the seed impact assessment in `config/local/codex-for-legal/ai-governance-legal/CLAUDE.md`. Use when user says "impact assessment for", "assess this AI use case", "run an AIA", "generate an AIA", "we need to document this AI system", "AI risk assessment for X", or follows a conditional triage result.
Run the cold-start interview — learns your AI governance practice and writes `config/local/codex-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".
Guided customization of your AI governance practice profile — change one thing without re-running the whole cold-start interview. Adjust risk posture, escalation contacts, use-case registry entries, vendor AI positions, AI policy commitments, impact-assessment house style, or matter workspace paths. Use when the user says "change my [thing]", "update my profile", "edit my config", "tune my playbook", or "customize".
Manage matter workspaces — new, list, switch, close, or detach (practice-level). File-management logic for keeping one client or engagement's context separate from every other. Use when working across multiple clients or matters, when the user says "new matter", "switch matter", "list matters", "close matter", or when any substantive skill needs to know which matter it's working in.
Keep the AI policy current with practice — weekly sweep of saved AIAs, triage results, and vendor reviews to find policy drift, or direct query for a proposed new AI practice. Use when user says "policy sweep", "does our AI policy cover this", "we want to start doing X — does the policy need updating", "run the policy monitor", or on a recurring schedule.