--- name: trussi-ai-production-and-calendar-check description: Check Trussi production orders, the job catalog and the calendar for a day or week, spotting double-booked crews, missing worksheets or supplements, and jobs with no scheduled activity, then draft any new appointment for approval instead of creating it. Use when the user asks what is on the production calendar tomorrow or this week, whether a crew is double-booked, which jobs are missing a worksheet or supplement, or what is scheduled for a job. --- # Check production and the calendar The question this skill answers is: **for this window, is every job that should be moving actually scheduled, staffed on paper and documented, and is anything booked twice?** Work from the calendar outward, then check each job's production paperwork. A calendar that looks full can still hide a job with no production order or a crew booked on two jobs at once. ## 1. Fix the window and the scope first Before pulling anything, pin down: - **The window.** A single day, a week, or "next 14 days". State the exact dates in your reply. - **The branch or location.** Call `trussi_list_locations` if the user has not named one, and confirm which location the results cover. Results from one branch must not be presented as company-wide. - **Whether the user means "scheduled" or "in production".** A calendar appointment and a production order are different records. Say which you are reporting on. ## 2. Pull the calendar, then the production orders Start with `trussi_list_calendar_events` for the window. Note each event's date, the job it relates to, and the crew or resource it names. Page through results until the window is covered; do not assume the first page is complete. Then call `trussi_list_production_orders` for the same window and branch. Match each production order to a calendar event where you can. Three mismatches matter most: - **Calendar event with no production order.** The appointment exists but nothing is ordered. Often a site visit, not a job, so check the event type before flagging it. - **Production order with no calendar event.** Work is ordered but not scheduled. This is the most common cause of a job that quietly slips. - **Two events for the same crew at overlapping times, or the same job booked twice.** A double-booking. Report the time overlap explicitly. ## 3. Check the job catalog for what the work actually is Use `trussi_list_job_catalog` to confirm the job types on the production orders and calendar. A production order for a job type not in the catalog is worth a question, not an assertion of error. Use the catalog to tell apart a roof replacement from a repair or an inspection, because a repair and a full replacement do not need the same crew time or supplements. ## 4. Verify each active job's paperwork For each job that is in the window, check the production documents on the job, not just the calendar: - `trussi_get_project` for the job's status and key facts. - `trussi_get_project_worksheets`: a job being built with no worksheet is a gap. Check whether it is simply not yet started (a job booked for next week is not a gap today). - `trussi_list_project_supplements`: an approved supplement that has not been reflected in the production order or schedule is a real risk. A pending supplement is a note, not a failure. - `trussi_list_project_activity` if you need to know when a job last moved, to tell a stalled job from a fresh one. ## 5. Sort the findings by what needs action Group the results so the user can act on the first group immediately: 1. **Conflicts:** double-booked crews, two jobs claiming the same slot. 2. **Gaps that will bite:** production orders with no schedule, approved supplements not yet in production, jobs starting in the window with no worksheet. 3. **Worth a look:** calendar events with no production order where the event type suggests a job, jobs with no scheduled activity at all in the window. 4. **Fine:** scheduled, ordered, documented. Count these, do not list them one by one. ## 6. Drafting a new appointment If the user wants a gap filled, prepare the appointment as a draft: job, date, time, crew, purpose, and the production order it relates to. Show the draft and ask. Creating it with `trussi_create_calendar_event` changes the live calendar that crews and customers see, so wait for the user's explicit yes, and confirm the exact time and crew again just before creating it. ## Common patterns and traps - **A full calendar is not a staffed plan.** A crew with three events on one day may have three jobs with no production orders. Always cross-check against orders. - **Pagination hides conflicts.** A double-booking can sit on page two. Only call a day clear after you have seen the whole window. - **Time zones and all-day events.** An all-day event has no start time, so it cannot prove an overlap. Say when an overlap depends on a time you could not confirm. - **Blaming the calendar for a paperwork gap.** A job with a scheduled crew and no worksheet is a documentation gap, not a scheduling failure. Name the right problem. - **Treating a pending supplement as an approved one.** Only an approved supplement changes scope. Pending ones are noted. - **Branch mix-ups.** A crew name may exist at two branches. Confirm the location before calling it a conflict. - **Reading a future job as overdue.** A job starting next Thursday with no worksheet today is probably on track. Check the start date before flagging it. ## Output ``` Window: , location: Conflicts () - :