anthropics/expansion-update
> 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.
npx skills add https://github.com/anthropics/claude-for-legal --skill expansion-update
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.
~/.claude/plugins/config/claude-for-legal/employment-legal/CLAUDE.md.~/.claude/plugins/config/claude-for-legal/employment-legal/expansion-[slug].yaml. If it doesn'texist, respond: "No expansion tracker found for [country]. Run
/employment-legal:expansion-kickoff [country] to start one."
[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]
> 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.
done,check whether it unblocks other items and flag those as now actionable.
open orin-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-expansion reference skill — load it before doing substantive
> work.
Take anthropics/expansion-update from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.