expansion-kickoff

Kick off international expansion planning by producing an EOR-versus-entity framing and writing an expansion YAML tracker.

Updated May 26, 2026
One-click install
npx skills add https://github.com/yachela/claude-for-legal-ar --skill expansion-kickoff-yachela
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expansion-kickoff
Source: https://github.com/yachela/claude-for-legal-ar/tree/main/employment-legal/skills/expansion-kickoff
Command: npx skills add https://github.com/yachela/claude-for-legal-ar --skill expansion-kickoff-yachela

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Expansion planning stalls when teams lack country-specific inputs and a clear EOR-versus-entity framing, especially at the moment of the first hire.

Core Features & Use Cases

  • EOR vs. Entity Framing: Establishes the right operating model for hiring in a new country by running a structured workflow.
  • Cross-Functional Question Drafting: Produces targeted questions to align stakeholders across HR, legal, finance, and operations.
  • Country-Specific Flags & Persistent Tracker: Surfaces jurisdictional flags and creates/uses a per-country tracker to maintain continuity from kickoff to updates.

Quick Start

Run the expansion kickoff for Germany by executing: /employment-legal:expansion-kickoff Germany

Frequently Asked Questions about expansion-kickoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I kick off international expansion and plan hiring in a new country?

Kick off international expansion by gathering cross-functional intake and producing an EOR-versus-entity operating model for the new country. The workflow loads local employment-legal profiles and writes a persistent per-country YAML tracker to maintain continuity from kickoff through updates.

What is the best way to decide between EOR vs entity when making first hires abroad?

Deciding between EOR and entity requires a structured framing workflow that evaluates country-specific employment-legal profiles and cross-functional intake. This approach establishes the right operating model by surfacing jurisdictional flags and drafting targeted alignment questions for HR, legal, and finance teams.

How do I draft cross-functional questions for stakeholders when expanding into a new jurisdiction?

Draft cross-functional questions by running a structured expansion kickoff workflow that produces targeted questions to align stakeholders across HR, legal, finance, and operations. The workflow evaluates country-specific jurisdictional flags and employment-legal profiles to ensure comprehensive alignment before the first hire.

Can I maintain a persistent tracker for international expansion planning across multiple updates?

You can maintain a persistent tracker for international expansion by writing an expansion-[slug].yaml file on workflow completion. The system validates existing tracker presence during kickoff and uses this per-country file to maintain continuity from initial planning through subsequent updates.

Does the expansion kickoff workflow require any existing trackers or dependencies to start?

The expansion kickoff workflow requires no external dependencies to start. It validates existing tracker presence during execution and loads the local employment-legal profile and international-expansion reference workflow internally to produce the EOR-versus-entity framing and cross-functional intake.