plan-eu-relocation
À propos
Cette Compétence Claude crée des chronologies structurées et tenant compte des dépendances pour les déménagements à l'intérieur ou vers la région UE/DACH. Elle cartographie les démarches administratives, suit les échéances et identifie les procédures spécifiques à chaque pays, produisant un plan unique de bout en bout. Utilisez-la pour les déménagements professionnels, la coordination avec des délais serrés, ou toute relocalisation complexe nécessitant un flux de travail visuel clair.
Installation rapide
Claude Code
Recommandénpx 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-relocationCopiez et collez cette commande dans Claude Code pour installer cette compétence
Documentation
Plan EU Relocation
Create a structured, dependency-aware relocation plan for moving within or to the EU/DACH region, covering bureaucratic steps, deadlines, and country-specific requirements.
When to Use
- Planning a move from one EU/DACH country to another
- Relocating from a non-EU country to an EU/DACH destination
- Needing to understand which bureaucratic steps depend on which before starting
- Coordinating employment-based relocation with employer HR
- Managing a relocation with tight deadlines (job start date, lease start, school enrollment)
- Wanting a single document that maps the entire relocation process end-to-end
Inputs
Required
- Origin country: Current country of residence
- Destination country: Target country (Germany, Austria, or Switzerland primarily; other EU supported)
- Nationality/nationalities: Citizenship(s) held, including EU/non-EU distinction
- Employment type: Employed (local contract), posted worker, self-employed, freelance, unemployed, student, or retired
- Target move date: Approximate date of physical relocation
- Household composition: Single, couple, family with children (ages), pets
Optional
- Job start date: First day of employment in destination country
- Housing status: Already secured, searching, employer-provided
- Current insurance coverage: Health, liability, household
- Language proficiency: Destination country language level (A1-C2 or none)
- Special circumstances: Disability, pregnancy, military service obligations, ongoing legal matters, custody arrangements
- Prior EU registrations: Previous Anmeldung or equivalent in other EU countries
Procedure
Step 1: Assess Situation
Gather all relevant personal, professional, and legal context to determine which bureaucratic tracks apply.
- Confirm EU vs. non-EU nationality status for all household members
- Determine if a visa or residence permit is required (non-EU nationals, non-EEA family members)
- Classify employment type and check if a work permit is needed separately from a residence permit
- Note any bilateral agreements between origin and destination countries (social security, tax treaties, recognition of qualifications)
- Identify whether the move is permanent, temporary (under or over 183 days), or cross-border commuting
- Record all fixed dates: job start, lease start, school year start, notice periods at current residence
Got: A structured profile document containing nationality status, employment classification, move type, and all fixed dates.
If fail: If nationality or employment status is ambiguous (e.g., dual nationality with one non-EU, or contractor vs. employee distinction unclear), escalate to a legal advisor or the destination country's embassy before proceeding. Do not guess visa requirements.
Step 2: Map Dependency Chain
Identify all bureaucratic steps and their prerequisites to establish the correct execution order.
- List all required registrations for the destination country:
- Residence registration (Anmeldung / Meldezettel / Anmeldung bei der Gemeinde)
- Tax registration or number assignment
- Health insurance enrollment
- Social security registration
- Bank account opening
- Vehicle re-registration (if applicable)
- School/childcare enrollment (if applicable)
- Pet import procedures (if applicable)
- List all deregistration steps for the origin country:
- Residence deregistration (Abmeldung or equivalent)
- Tax office notification
- Insurance cancellations or transfers
- Utility cancellations
- Mail forwarding
- Map dependencies as a directed acyclic graph (DAG):
- Residence registration typically depends on having a signed lease
- Tax number depends on residence registration
- Bank account may depend on residence registration and tax number
- Health insurance enrollment may depend on employment contract or residence registration
- Social security coordination depends on employment classification
- Identify parallel tracks: steps that can proceed simultaneously
- Mark steps that require in-person appointments vs. those that can be done online or by mail
Got: A dependency graph (textual or visual) showing all steps, their prerequisites, and which can run in parallel.
If fail: If dependencies are unclear for a specific country, search for official government sources (e.g., Germany: bmi.bund.de, Austria: oesterreich.gv.at, Switzerland: ch.ch). Do not assume dependencies transfer between countries.
Step 3: Create Timeline with Deadlines
Convert the dependency graph into a calendar-based timeline aligned with the target move date.
- Work backwards from the move date and any fixed deadlines (job start, school year)
- For each step, estimate:
- Lead time (how early it can be started)
- Processing time (how long the authority takes)
- Buffer time (recommended slack for delays)
- Assign calendar windows to each step:
- Pre-move actions (can be done from origin country): visa application, insurance research, document preparation
- Move-week actions: Anmeldung, bank account, SIM card
- Post-move actions (within legal deadlines): tax registration, vehicle re-registration, deregistration at origin
- Note statutory deadlines with penalties:
- Germany: Anmeldung within 14 days of moving in
- Austria: Meldezettel within 3 days
- Switzerland: Anmeldung within 14 days (varies by canton)
- Tax registration deadlines vary
- Add appointment booking lead times (some Buergeramt offices require 2-6 weeks advance booking)
Got: A week-by-week timeline spanning from 8-12 weeks before the move to 4-8 weeks after, with each bureaucratic step placed in its execution window.
If fail: If appointment availability is unpredictable (common in large German cities), build in a 2-week buffer and identify alternative offices or early-morning walk-in options.
Step 4: Identify Country-Specific Procedures
Tailor the generic plan to the specific destination country's requirements and conventions.
- For Germany:
- Buergeramt Anmeldung (requires Wohnungsgeberbestaetigung from landlord)
- Finanzamt tax ID assignment (Steueridentifikationsnummer arrives by mail in 2-4 weeks)
- Gesetzliche or private Krankenversicherung enrollment
- Rentenversicherung coordination
- Rundfunkbeitrag (GEZ) registration
- Elterngeld/Kindergeld applications if applicable
- For Austria:
- Meldezettel at Meldeamt (within 3 days)
- Finanzamt registration for Steuernummer
- e-card for health insurance (through employer or self-registration with OeGK)
- Sozialversicherung coordination
- For Switzerland:
- Einwohnerkontrolle registration (within 14 days, canton-dependent)
- AHV/IV/EO social insurance registration
- Mandatory health insurance (Grundversicherung) within 3 months
- Quellensteuer or regular tax depending on permit type
- Residence permit (B or L) application through employer or canton
- Cross-reference each procedure with the documents required (see check-relocation-documents skill)
Got: A country-specific procedure list with exact office names, required forms, and typical processing times.
If fail: If destination is a smaller municipality, procedures may differ from the national standard. Check the specific Gemeinde/Kommune website or call their Buergerservice directly.
Step 5: Flag High-Risk Items
Identify steps where missed deadlines carry financial penalties, legal consequences, or cascading delays.
- Mark all steps with statutory deadlines (Anmeldung, tax registration, insurance enrollment)
- Calculate the penalty for missing each deadline:
- Late Anmeldung in Germany: fine up to 1,000 EUR
- Late Meldezettel in Austria: fine up to 726 EUR
- Late health insurance in Switzerland: retroactive premiums plus surcharge
- Identify bottleneck steps that block multiple downstream actions:
- No Anmeldung = no tax ID = no proper payroll = no bank account (in some cases)
- Flag items requiring original documents that are hard to replace if lost (birth certificates, marriage certificates, degree attestations)
- Note seasonal risks: end-of-year moves conflict with office closures; September moves coincide with school enrollment pressure
- Identify steps where the origin country has a deadline too (deregistration, tax year coordination, insurance notice periods)
Got: A risk register with each high-risk item, its deadline, penalty, and mitigation strategy.
If fail: If penalty amounts or deadlines cannot be confirmed through official sources, mark them as "unconfirmed" and recommend direct inquiry with the relevant authority. Do not invent penalty amounts.
Step 6: Generate Relocation Plan Document
Compile all findings into a single actionable relocation plan.
- Structure the document with these sections:
- Executive summary (move type, key dates, household composition)
- Dependency graph (visual or textual)
- Timeline (week-by-week checklist)
- Country-specific procedures (destination)
- Deregistration procedures (origin)
- Risk register (high-priority items highlighted)
- Document checklist (cross-reference to check-relocation-documents)
- Contact list (relevant offices, phone numbers, appointment URLs)
- Format each checklist item with:
- Status indicator (not started / in progress / done / blocked)
- Deadline
- Dependencies
- Notes or tips
- Include a "first 48 hours" quick-reference card for the most time-critical steps after arrival
- Add a "what-if" section for common disruptions: apartment falls through, job start date changes, documents delayed in mail
Got: A complete, structured relocation plan document ready for execution, with all items traceable back to the dependency graph and risk register.
If fail: If the plan is too complex for a single document (e.g., multi-country move with dependents requiring separate visa tracks), split into a master timeline and per-person sub-plans.
Validation
- Every bureaucratic step in the dependency graph has at least one source (official government website, embassy, or legal reference)
- All statutory deadlines are noted with their legal basis
- The timeline accounts for weekends, public holidays, and office closure periods
- No step appears before its dependencies in the timeline
- The risk register covers at minimum: Anmeldung, tax registration, health insurance, and social security
- The document checklist cross-references the check-relocation-documents skill output
- Fixed dates (job start, lease start) are reflected in the timeline without conflicts
Pitfalls
- Assuming all EU countries have the same procedures: Registration deadlines, required documents, and office structures vary significantly even within DACH
- Underestimating appointment lead times: In Berlin, Hamburg, and Munich, Buergeramt appointments can be booked out 4-6 weeks; plan accordingly or use walk-in slots
- Forgetting the origin country: Deregistration, tax notifications, and insurance cancellation periods at the origin are just as important as destination registrations
- Ignoring the 183-day tax rule: Spending more than 183 days in a country in a calendar year typically triggers full tax residency; coordinate the move date carefully
- Not bringing originals: Many DACH offices require original documents (not copies) and some require certified translations; digital copies are often not accepted
- Treating Switzerland like an EU country: Switzerland is not in the EU; different rules apply for residence permits, health insurance, and social security, even for EU nationals
- Missing the health insurance gap: Between leaving origin country insurance and enrolling in destination country insurance, there may be an uncovered period; arrange travel or international health insurance to bridge it
- Overlooking pet regulations: Pet passports, rabies titers, and breed-specific import rules can add weeks to the timeline
Related Skills
- check-relocation-documents -- Verify document completeness for each bureaucratic step
- navigate-dach-bureaucracy -- Detailed guidance for specific DACH governmental procedures
Dépôt GitHub
Compétences associées
railway-docs
DocumentationCette compétence récupère la documentation actuelle de Railway pour répondre aux questions sur les fonctionnalités, le fonctionnement ou des URL spécifiques de la documentation. Elle garantit que les développeurs reçoivent des informations précises et à jour directement depuis les sources officielles de Railway. Utilisez-la lorsque les utilisateurs demandent comment fonctionne Railway ou font référence à la documentation de Railway.
n8n-code-python
DocumentationCette compétence Claude offre un accompagnement expert pour écrire du code Python dans les nœuds Code de n8n, en particulier pour utiliser la bibliothèque standard de Python et travailler avec la syntaxe spéciale de n8n comme `_input`, `_json` et `_node`. Elle aide les développeurs à comprendre les limites de Python dans n8n et recommande d'utiliser JavaScript pour la plupart des workflows, tout en proposant des solutions Python pour des besoins spécifiques de transformation de données.
archon
DocumentationLa compétence Archon offre une recherche sémantique alimentée par RAG et une gestion de projet via une API REST. Utilisez-la pour interroger la documentation, gérer des projets/tâches hiérarchiques et effectuer de la recherche de connaissances avec des capacités de téléchargement de documents. Priorisez toujours Archon en premier lors de la recherche dans une documentation externe avant d'utiliser d'autres sources.
n8n-code-javascript
DocumentationCette compétence Claude fournit des conseils d'expert pour écrire du code JavaScript dans les nœuds Code d'n8n. Elle couvre la syntaxe essentielle spécifique à n8n comme les variables `$input`/`$json`, les assistants HTTP et la gestion des DateTime, tout en résolvant les erreurs courantes. Utilisez-la lors du développement de workflows n8n nécessitant un traitement JavaScript personnalisé dans les nœuds Code.
