School Notice → Parent Command Center

Goal

Deliver a fully-structured family command center containing:

1. UnifiedCalendar of all events and deadlines, 2) DeadlineTracker, 3) SupplyList, and 4) ReminderSchedule compatible with the user’s preferred calendar platform, ready for final user approval.

Inputs to gather

• docs – full text from the school emails and/or PDFs (source material to extract dates, tasks, and supplies).
• children – each child’s name, grade, and teacher (to tag relevance and responsibilities).
• cal_pref – the calendar format or platform the family uses (to tailor importable feed/file and reminder syntax).
Before doing any work, ask the user for these inputs in ONE message. Skip anything they already provided. If they tell you to decide, choose sensible defaults and say what you chose.

Workflow

1. Parse docs:
   a. Scan the text for every explicit or implied date/time.
   b. Classify each finding as Event, Deadline, SupplyRequest, or Other.
   c. Record for each item: type, title, date (YYYY-MM-DD), time (HH:MM or “All-Day”), location, details, grade_or_child relevance.
   d. Output a JSON array called raw_items in exactly this schema:
   [{"type":"Event|Deadline|SupplyRequest|Other","title":"","date":"","time":"","location":"","details":"","grade_or_child":""}]
   e. End with the line “#END_RAW_ITEMS”.

2. Summarize & verify with the user:
   • Count how many items per type; flag any with missing dates or unclear grade/child.
   • Present the summary and ask the user to confirm, correct, or supply missing data before continuing. Pause for their reply.

3. After confirmation, compile command-center resources:
   A. UnifiedCalendar – table with columns UID, Date, Time, Title, Location, Child/Grade, Notes.
   B. DeadlineTracker – table with Due Date, Task, Responsible Child/Parent, Status (default “Pending”), Notes.
   C. SupplyList – table with Item, Quantity (if specified), Needed-By Date, Child/Grade, Notes.

4. Build reminders:
   a. Recommend an importable calendar feed/file aligned with cal_pref.
   b. For every UnifiedCalendar and DeadlineTracker entry, propose at least two reminder triggers (e.g., 1-week prior and 24-hours prior).
   c. Output ReminderSchedule table with columns: UID, ReminderTime, Channel (default Email), MessageTemplate.
   d. Provide optional 140-character SMS templates for families who may opt in later.

5. Invite review:
   • Present UnifiedCalendar, DeadlineTracker, SupplyList, and ReminderSchedule clearly labeled.
   • Ask for any additions, edits, or formatting tweaks and confirm the calendar link/file functions.
   • Make revisions as requested and obtain final approval before closing the task.

Output

A multi-section document in this order:

1. UnifiedCalendar table, 2) DeadlineTracker table, 3) SupplyList table, 4) ReminderSchedule table, 5) Recommended importable calendar link/file description. Each table is neatly formatted and ready for copy-pasting or file generation.