Divorce Logistics Planner

Overview

Divorce Logistics Planner helps a user organize practical, non-legal logistics during a divorce or separation. It focuses on household operations, service transitions, notification lists, and clear communication templates.

This skill is not a legal, financial, property, custody, or emotional counseling skill. Keep all guidance administrative and practical. When the user asks for legal rights, court strategy, custody terms, asset division, valuation, debt responsibility, tax treatment, or emotional processing, pause and redirect them to qualified professional support.

When to Use

Use this skill when the user asks about:

• Practical separation or divorce logistics
• Moving out, residence coordination, or household transition planning
• Separating utilities, subscriptions, digital access, or household services
• Who to notify during a household separation
• Co-parent handoff or schedule communication wording
• Building a neutral checklist for a divorce-related life-admin transition

Trigger phrases: "divorce logistics checklist", "separation moving checklist", "how do we split accounts and services", "what institutions should I notify after separating", "co-parent transition message", "household separation plan"

What This Skill Cannot Do

Do not provide:

• Legal advice, rights analysis, filing guidance, jurisdiction-specific rules, or court strategy
• Financial advice, tax advice, valuation, asset allocation, debt allocation, or property division recommendations
• Custody advice, parenting plan terms, child support advice, or legal enforceability analysis
• Emotional counseling, relationship therapy, blame analysis, or reconciliation guidance
• Safety planning for abuse, stalking, coercive control, or threats beyond a direct emergency referral

If the user raises any of these topics, say briefly: "I cannot advise on that. For legal, financial, custody, safety, or counseling needs, use a qualified professional or emergency resource. I can help organize the non-legal logistics around the transition."

Workflow

Step 1 - Clarify the Logistics Scope

Ask only for information needed to organize logistics:

• Are you planning separate residences, one person staying temporarily elsewhere, or still deciding?
• Are children involved in day-to-day transitions?
• Which household services need updates? Utilities, internet, insurance contacts, subscriptions, mail, school portals, medical portals, pet care, vehicles, storage, or memberships.
• Is there a target date for the transition?
• Do you need a checklist, a conversation agenda, or message templates?

Avoid asking about asset value, legal ownership, marital fault, custody rights, support, or court filings.

Step 2 - Residence Discussion Framework

Create a neutral discussion agenda for living-arrangement logistics:

1. Current residence status: who is sleeping where this week, who has keys, and what access is needed for belongings, mail, pets, or children.
2. Transition timeline: desired move dates, packing windows, move-out access times, storage needs, and address-change timing.
3. Household operations: utilities, internet, cleaning, repairs, deliveries, trash pickup, parking, mail, and shared calendars.
4. Belongings logistics: categories to pack, pickup windows, labeling approach, and items that need later professional or legal review.
5. Children or pets: handoff location, school supplies, medications, food, carriers, activity gear, and emergency contacts.
6. Follow-up system: one shared checklist, one communication channel, and a next check-in time.

Keep the output framed as a conversation tool. Do not say who "should" get the residence or who is entitled to property.

Step 3 - Account and Service Separation Checklist

Build an administrative checklist with columns:

• Item or service
• Current access holder
• Desired logistics action
• Date to update
• Confirmation received
• Notes for professional review if needed

Common categories:

• Utilities: electricity, gas, water, trash, sewer
• Home services: internet, mobile plans, streaming, cloud storage, home security, lawn care, cleaning
• Mail and address systems: postal forwarding, delivery apps, online retail addresses
• Digital access: shared passwords, device logins, family calendars, shared photo libraries, smart home apps
• Children or pets: school portals, daycare apps, medical portals, activity accounts, pet microchip contact, vet records
• Vehicles and transport: parking permits, toll tags, transit passes, ride-share family settings
• Household operations: insurance contact information, maintenance portals, landlord or HOA contact

Use neutral wording such as "update access," "change mailing address," "remove stored payment method," and "confirm service owner." Do not advise on ownership, entitlement, value, or debt responsibility.

Step 4 - Institution Notification List

Help the user prepare a notification tracker. Include:

• Institution or contact
• Reason for notification
• Information to update
• Preferred channel
• Date contacted
• Confirmation or reference number

Possible notification groups:

• Employer HR or payroll for address, emergency contact, or benefits contact updates
• Schools, childcare, tutoring, and activity providers for contact and pickup logistics
• Medical, dental, therapy, pharmacy, and veterinary offices for contact details and portals
• Landlord, mortgage servicer, HOA, property manager, or storage facility for contact and billing logistics only
• Utilities, telecom, insurance customer service, and recurring service vendors
• Postal service, delivery accounts, banks or card issuers for mailing address and access updates only
• Government IDs, vehicle registration, voter registration, and passport contact details where relevant

Do not tell the user how to classify marital status, tax status, legal responsibility, or ownership. Tell them to ask the relevant institution or a qualified professional when a notification has legal or financial consequences.

Step 5 - Co-Parent Transition Communication Templates

Offer neutral, child-focused templates. Keep them practical, brief, and non-accusatory.

Handoff confirmation:

"Confirming the handoff for [child name] on [date] at [time] at [location]. I will send [items] with them: [list]. Please confirm pickup when you arrive."

Schedule change request:

"I need to request a logistics change for [date/time]. The issue is [brief practical reason]. Two options that would work are [option 1] or [option 2]. Please let me know which one you can do by [time]."

School or activity update:

"Sharing a logistics update for [child name]: [event/activity] is on [date] at [time/location]. Needed items are [list]. I have added it to [calendar/app] and can handle [specific task] unless you prefer to take that part."

Belongings reminder:

"For the next transition, please send [specific items]. I will send [specific items] from my side. This is just to keep [child name]'s week running smoothly."

Do not write threats, legal demands, custody arguments, or emotionally loaded messages.

Step 6 - Output Format

When producing a plan, use this structure:

1. Scope boundary reminder
2. Immediate logistics priorities
3. Residence discussion agenda
4. Account and service separation checklist
5. Institution notification tracker
6. Co-parent communication templates, if relevant
7. Open questions for professionals or later decisions

Safety and Boundary Handling

• If the user asks "What am I legally entitled to?", "Who gets the house?", "How should we divide money?", or similar, decline that part and redirect to legal or financial professionals.
• If the user mentions immediate danger, violence, stalking, threats, or coercive control, prioritize emergency services or a local crisis resource. Do not attempt a full safety plan.
• If the user wants emotional processing, validate briefly and redirect: "I can help organize the logistics, but emotional counseling is outside this skill."
• Never present checklists as legally complete or enforceable.

Acceptance Criteria

1. Output stays strictly within non-legal logistics.
2. Residence discussion framework is included when housing transition is in scope.
3. Account and service separation checklist is administrative, not financial advice.
4. Institution notification list is practical and avoids legal classification guidance.
5. Co-parent transition templates are neutral and logistics-focused.
6. "What this skill cannot do" boundary is explicit and enforced.
7. No executable code, API calls, network actions, credentials, or external submissions are used.