plan-eu-relocation
About
This skill creates structured, dependency-aware timelines for relocations to or within the EU/DACH region. It maps bureaucratic steps, tracks deadlines, and handles country-specific procedures. Use it for coordinating complex moves, especially when integrating with employer HR or managing tight deadlines.
Quick Install
Claude Code
Recommendednpx skills add pjt222/agent-almanac -a claude-code/plugin add https://github.com/pjt222/agent-almanacgit clone https://github.com/pjt222/agent-almanac.git ~/.claude/skills/plan-eu-relocationCopy and paste this command in Claude Code to install this skill
Documentation
Plan EU Relocation
Structured, dependency-aware relocation plan for EU/DACH moves → bureaucratic steps, deadlines, country-specific reqs.
Use When
- Move EU/DACH → EU/DACH
- Non-EU → EU/DACH
- Need step dependencies before start
- Coord employment relocation w/ employer HR
- Tight deadlines (job start, lease, school)
- Want single end-to-end doc
In
Required
- Origin country: Current residence
- Destination: Target (Germany, Austria, Switzerland primary; other EU OK)
- Nationality: Citizenship(s), EU/non-EU
- Employment type: Employed (local), posted, self-employed, freelance, unemployed, student, retired
- Move date: Approx physical move
- Household: Single, couple, family w/ kids (ages), pets
Optional
- Job start date: First day in destination
- Housing: Secured, searching, employer-provided
- Insurance: Health, liability, household
- Language: Destination level (A1-C2 or none)
- Special: Disability, pregnancy, military, legal matters, custody
- Prior EU regs: Previous Anmeldung or equivalent
Do
Step 1: Assess Situation
Gather personal, professional, legal context → which bureaucratic tracks apply.
- EU vs non-EU status, all members
- Visa or residence permit needed? (non-EU, non-EEA family)
- Employment type → work permit separate from residence permit?
- Bilateral agreements (social security, tax treaties, qualification recognition)
- Move type: permanent, temp (under/over 183 days), cross-border commute
- Fixed dates: job start, lease start, school year, notice periods
→ Profile doc: nationality, employment, move type, fixed dates.
If err: nationality or employment ambiguous (dual w/ one non-EU, contractor vs employee unclear) → escalate to legal advisor or destination embassy. No guessing visa reqs.
Step 2: Map Dependency Chain
Bureaucratic steps + prereqs → correct execution order.
- Destination registrations:
- Residence reg (Anmeldung / Meldezettel / Anmeldung bei der Gemeinde)
- Tax reg or number assignment
- Health insurance enroll
- Social security reg
- Bank account
- Vehicle re-reg (if applicable)
- School/childcare enroll (if applicable)
- Pet import (if applicable)
- Origin deregistration:
- Residence dereg (Abmeldung or equivalent)
- Tax office notif
- Insurance cancel/transfer
- Utility cancel
- Mail forward
- Map deps as DAG:
- Residence reg → needs signed lease
- Tax number → needs residence reg
- Bank account → may need residence reg + tax number
- Health insurance → may need employment contract or residence reg
- Social security coord → depends on employment type
- Find parallel tracks → simultaneous steps
- Mark in-person vs online/mail steps
→ Dependency graph (textual or visual): all steps, prereqs, parallels.
If err: deps unclear for country → search official sources (Germany: bmi.bund.de, Austria: oesterreich.gv.at, Switzerland: ch.ch). Never assume cross-country transfer.
Step 3: Create Timeline w/ Deadlines
Dependency graph → calendar timeline aligned w/ move date.
- Backwards from move date + fixed deadlines (job, school)
- Per step, estimate:
- Lead time (earliest start)
- Processing time (authority duration)
- Buffer time (slack for delays)
- Calendar windows:
- Pre-move (from origin): visa, insurance research, doc prep
- Move-week: Anmeldung, bank, SIM
- Post-move (within legal deadlines): tax reg, vehicle re-reg, origin dereg
- Statutory deadlines + penalties:
- Germany: Anmeldung within 14 days
- Austria: Meldezettel within 3 days
- Switzerland: Anmeldung within 14 days (canton varies)
- Tax reg deadlines vary
- Appointment lead times (some Buergeramt → 2-6 weeks advance)
→ Week-by-week timeline 8-12 wks pre-move to 4-8 wks post, each step in its window.
If err: appointment availability unpredictable (big German cities) → 2-week buffer, alt offices or early-morning walk-ins.
Step 4: Identify Country-Specific Procedures
Tailor generic plan to destination's reqs + conventions.
- Germany:
- Buergeramt Anmeldung (needs Wohnungsgeberbestaetigung from landlord)
- Finanzamt tax ID (Steueridentifikationsnummer by mail in 2-4 wks)
- Gesetzliche or private Krankenversicherung enroll
- Rentenversicherung coord
- Rundfunkbeitrag (GEZ) reg
- Elterngeld/Kindergeld if applicable
- Austria:
- Meldezettel at Meldeamt (within 3 days)
- Finanzamt → Steuernummer
- e-card health insurance (employer or self-reg w/ OeGK)
- Sozialversicherung coord
- Switzerland:
- Einwohnerkontrolle reg (within 14 days, canton-dependent)
- AHV/IV/EO social insurance reg
- Mandatory health insurance (Grundversicherung) within 3 mo
- Quellensteuer or regular tax (permit-dependent)
- Residence permit (B or L) via employer or canton
- Cross-ref each procedure w/ docs needed (see check-relocation-documents)
→ Country-specific list: exact office names, forms, processing times.
If err: smaller municipality → procedures may differ from national standard. Check Gemeinde/Kommune website or call Buergerservice direct.
Step 5: Flag High-Risk Items
Steps where missed deadlines → fines, legal consequences, cascading delays.
- Mark all w/ statutory deadlines (Anmeldung, tax reg, insurance enroll)
- Penalty per missed deadline:
- Late Anmeldung Germany: fine up to 1,000 EUR
- Late Meldezettel Austria: fine up to 726 EUR
- Late health insurance Switzerland: retroactive premiums + surcharge
- Bottleneck steps blocking downstream:
- No Anmeldung = no tax ID = no payroll = no bank account (sometimes)
- Flag items needing originals hard to replace (birth, marriage, degree)
- Seasonal risks: end-of-year → office closures; September → school enrollment pressure
- Origin deadlines (dereg, tax year coord, insurance notice periods)
→ Risk register: each item, deadline, penalty, mitigation.
If err: penalty/deadlines unconfirmable from official sources → mark "unconfirmed", recommend direct inquiry. No invented penalties.
Step 6: Generate Relocation Plan Doc
Compile findings → single actionable plan.
- Sections:
- Exec summary (move type, dates, household)
- Dependency graph (visual or textual)
- Timeline (week-by-week checklist)
- Country-specific procedures (destination)
- Dereg procedures (origin)
- Risk register (high-pri highlighted)
- Doc checklist (cross-ref check-relocation-documents)
- Contact list (offices, phones, appointment URLs)
- Per checklist item:
- Status (not started / in progress / done / blocked)
- Deadline
- Deps
- Notes/tips
- "First 48 hours" quick-ref card → most time-critical post-arrival
- "What-if" section: common disruptions (apt falls through, job date changes, mail delays)
→ Complete plan doc ready to execute, all items traceable to graph + risk register.
If err: too complex for single doc (multi-country w/ separate visa tracks per dependent) → master timeline + per-person sub-plans.
Check
- Every step in graph has source (official site, embassy, legal ref)
- All statutory deadlines noted w/ legal basis
- Timeline accounts for weekends, holidays, closures
- No step before its deps
- Risk register covers min: Anmeldung, tax reg, health insurance, social security
- Doc checklist cross-refs check-relocation-documents
- Fixed dates (job, lease) in timeline w/o conflicts
Traps
- Assume all EU same procedures: Deadlines, docs, office structures vary even within DACH
- Underestimate appointment leads: Berlin/Hamburg/Munich Buergeramt → 4-6 wks booking; plan or use walk-ins
- Forget origin country: Dereg, tax notifs, insurance cancel periods at origin = as important as destination
- Ignore 183-day tax rule: >183 days in country/yr → full tax residency. Coord move date.
- No originals: DACH offices need originals (not copies), some need certified translations. Digital often not accepted.
- Treat Switzerland like EU: Not in EU. Different rules for residence permits, health, social — even for EU nationals.
- Health insurance gap: Between origin cancel + destination enroll → uncovered period. Travel/international insurance to bridge.
- Overlook pet rules: Pet passports, rabies titers, breed-specific import → adds weeks.
→
- check-relocation-documents — verify doc completeness per step
- navigate-dach-bureaucracy — detailed DACH gov procedures
GitHub Repository
Frequently asked questions
What is the plan-eu-relocation skill?
plan-eu-relocation is a Claude Skill by pjt222. Skills package instructions and resources that Claude loads on demand, so Claude can perform plan-eu-relocation-related tasks without extra prompting.
How do I install plan-eu-relocation?
Use the install commands on this page: add plan-eu-relocation to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.
What category does plan-eu-relocation belong to?
plan-eu-relocation is in the Documentation category, tagged general.
Is plan-eu-relocation free to use?
Yes. plan-eu-relocation is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.
Related Skills
This skill fetches current Railway documentation to answer questions about features, functionality, or specific docs URLs. It ensures developers receive accurate, up-to-date information directly from Railway's official sources. Use it when users ask how Railway works or reference Railway documentation.
This Claude Skill provides expert guidance for writing Python code in n8n's Code nodes, specifically for using Python's standard library and working with n8n's special syntax like `_input`, `_json`, and `_node`. It helps developers understand Python's limitations within n8n and recommends using JavaScript for most workflows while offering Python solutions for specific data transformation needs.
The Archon skill provides RAG-powered semantic search and project management through a REST API. Use it for querying documentation, managing hierarchical projects/tasks, and performing knowledge retrieval with document upload capabilities. Always prioritize Archon first when searching external documentation before using other sources.
This Claude Skill provides expert guidance for writing JavaScript code in n8n's Code nodes. It covers essential n8n-specific syntax like `$input`/`$json` variables, HTTP helpers, and DateTime handling, while troubleshooting common errors. Use it when developing n8n workflows that require custom JavaScript processing in Code nodes.
