AI Family Schedule Conflict Board

Overview

Use this skill when a parent, guardian, caregiver, or household coordinator needs to compare family schedules and spot conflicts before they become missed pickups, double bookings, or overloaded days.

This is a prompt-only planning skill. It uses only schedules, constraints, and preferences supplied by the user in the conversation. Keep private schedules local and user-supplied. Do not access calendars, invite people, update calendar systems, send messages, or contact anyone. Any message drafts are for review only and must be explicitly approved and sent by the user outside this skill.

Trigger

Use this skill when the user asks to:

• Compare family schedules for a day, week, weekend, trip, school term, or activity season.
• Find double bookings, overlaps, pickup or drop-off conflicts, transportation gaps, or supervision gaps.
• Decide which event takes priority when two family obligations compete.
• Create a shared schedule board for caregivers, parents, teens, relatives, sitters, or drivers.
• Draft coordination messages for family members, caregivers, teachers, coaches, or activity leaders.

Do not use this skill to pull calendar data, monitor private calendars, send automated messages, make unilateral family decisions, or manage legal custody arrangements.

Intake

Ask for only the information needed to build the board:

• Date range and timezone, if relevant.
• Family members or roles to include.
• User-provided schedule entries: date, start time, end time, person, location, travel time, required attendees, and flexibility.
• Hard constraints, such as school pickup windows, work meetings, appointment times, custody handoff times, or medication reminders supplied by the user.
• Soft preferences, such as avoiding back-to-back drives, protecting homework time, or preserving dinner together.
• Available helpers, backup drivers, rideshares, carpools, or remote options supplied by the user.
• Priority rules the family already uses, or permission to propose a draft priority ladder.

If the schedule is incomplete, proceed with an assumptions list and mark unknowns instead of inventing details.

Workflow

1. Normalize the schedule. Convert user-provided entries into a clear timeline with date, time, person, location, travel buffer, flexibility, and owner.
2. Create the conflict board. Group entries by day and time, then identify hard conflicts, soft conflicts, travel risks, coverage gaps, and overloaded periods.
3. Classify severity. Label each issue as critical, high, medium, or low based on time overlap, required attendance, safety or supervision impact, and flexibility.
4. Check coverage. Identify who is responsible for pickup, drop-off, supervision, meals, homework, pets, household coverage, or dependent care when those details are supplied.
5. Propose options. For each conflict, list practical choices such as shift time, swap driver, request remote attendance, carpool, skip optional event, split attendance, or ask for help.
6. Apply priority rules. Use user-provided rules first. If none are given, suggest a draft ladder that prioritizes safety, required school or medical obligations, immovable one-time events, work commitments, recurring optional events, and preferences.
7. Draft review-only messages. When useful, create short drafts for the user to review, edit, and send manually. Clearly label them as drafts.
8. Produce an action list. Separate decisions needed now, messages to review, calendar updates the user must make, and watch items.

Output Format

Return these sections:

1. Schedule Snapshot: date range, people, sources supplied by the user, timezone, and assumptions.
2. Conflict Board: table or bullet board with time, people affected, conflict type, severity, and evidence.
3. Coverage Gaps: pickup, drop-off, supervision, travel, meal, homework, or household gaps.
4. Decision Options: options for each conflict with trade-offs and owner.
5. Suggested Priority Ladder: user-provided rules or a clearly labeled draft.
6. Action List: decisions, calendar updates for the user, confirmations needed, and watch items.
7. Message Drafts for Review: optional drafts labeled """Review before sending."""
8. Privacy and Scope Notes: user-provided schedules only, no automatic sending, and private details stay local.

If the user only needs a quick answer, put the highest-risk conflicts first and keep the rest compact.

Conflict Types

Use these labels consistently:

• Hard overlap: One person is required in two places at the same time.
• Travel impossibility: Travel time makes an otherwise non-overlapping schedule unworkable.
• Coverage gap: A dependent, pickup, handoff, pet, household task, or supervision need has no owner.
• Back-to-back strain: The schedule is possible but brittle because of no buffer.
• Priority collision: Two important commitments compete and require a family decision.
• Information gap: A missing time, location, owner, or policy prevents a reliable plan.

Message Draft Rules

• Draft messages only when the user asks or when coordination is clearly needed.
• Label every draft as """Review before sending."""
• Keep drafts factual and flexible. Do not pressure recipients or imply commitments not supplied by the user.
• Do not send, schedule, post, email, text, or submit messages.
• Do not impersonate another family member, school staff member, coach, clinician, employer, or caregiver.

Safety Boundaries

• Use only user-provided schedule information. Do not access calendars, email, school portals, messaging apps, maps, or location services.
• Keep private schedules local and minimize sensitive details in shared outputs.
• No automatic calendar edits, invitations, reminders, messages, payments, forms, or contacts.
• Do not make legal, custody, medical, employment, or school-policy determinations.
• For high-conflict, legal, medical, or safety-sensitive situations, encourage the user to verify with the appropriate professional or institution.

Acceptance Criteria

1. Builds a clear conflict board from user-provided family schedule entries.
2. Identifies hard overlaps, travel impossibilities, coverage gaps, priority collisions, and information gaps.
3. Separates critical conflicts from soft or low-risk schedule strain.
4. Provides practical decision options and a reviewable action list.
5. Drafts coordination messages only for user review and never sends or automates them.
6. Keeps private schedules local and user-supplied, with no calendar, network, credential, or API dependency.

Example Prompts

• "Here are our schedules for next Thursday. Find conflicts and make a coverage plan."
• "Can you compare soccer, dentist, work meetings, and school pickup this week?"
• "Build a conflict board for our weekend with two kids and one car."
• "Draft a message asking another parent about carpool, but do not send it."
• "We have three events at 5 PM. Help us choose a plan."