expansion-kickoff

Coordinate EOR vs. entity evaluation and create an expansion tracker file.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kick off international expansion planning for a new country — gathers intake, runs EOR vs. entity framing, drafts cross-functional questions, surfaces country-specific flags, and creates a persistent tracker.

Core Features & Use Cases

  • Initiates an expansion project by collecting country-specific requirements, evaluating EOR vs. entity options, drafting cross-functional questions, surfacing flags, and establishing a persistent tracker.
  • Applies when leadership signals expansion ("we're hiring in [country]" or "expansion to [country]") to coordinate cross-functional readiness.
  • Generates a country-specific tracker file to guide implementation and governance.

Quick Start

Load the jurisdictional footprint data and the international-expansion reference, then run the kickoff command for the target country.

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 planning for a new country?▼

International expansion planning requires gathering intake, evaluating EOR vs. entity options, drafting cross-functional readiness questions, surfacing country-specific flags, and generating a persistent tracker file.

What is the difference between using an EOR and setting up an entity when expanding abroad?▼

EOR vs. entity evaluation compares using an Employer of Record for faster hiring against establishing a legal entity for direct employment, framing the regulatory and compliance implications for your expansion target country.

How do I track cross-functional readiness for international hiring?▼

Track cross-functional readiness for international hiring by generating a persistent expansion tracker file that documents country-specific flags, compliance requirements, and governance questions for all stakeholders.

When should I start compliance workflows for expanding to a new country?▼

Start compliance workflows when leadership signals international expansion or first hires abroad, triggering regulatory assessment, cross-functional readiness checks, and tracker governance for the target country.

Do I need jurisdictional footprint data before planning international expansion?▼

Yes, jurisdictional footprint data is loaded from the profile alongside an international-expansion reference to accurately surface country-specific flags and evaluate EOR vs. entity options during kickoff.

What are the limitations of using automated workflows for international expansion compliance?▼

Automated expansion workflows rely on loaded jurisdictional footprint data and reference skills, meaning missing profile data or reference gaps may limit country-specific flag surfacing and regulatory assessment accuracy.