Install
openclaw skills install divorce-logistics-plannerPlan non-legal divorce and separation logistics with residence discussion prompts, account and service separation checklists, institution notification lists, and co-parent transition communication templates.
openclaw skills install divorce-logistics-plannerDivorce 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.
Use this skill when the user asks about:
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"
Do not provide:
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."
Ask only for information needed to organize logistics:
Avoid asking about asset value, legal ownership, marital fault, custody rights, support, or court filings.
Create a neutral discussion agenda for living-arrangement logistics:
Keep the output framed as a conversation tool. Do not say who "should" get the residence or who is entitled to property.
Build an administrative checklist with columns:
Common categories:
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.
Help the user prepare a notification tracker. Include:
Possible notification groups:
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.
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.
When producing a plan, use this structure: