Lay out the dated session program for a package
design_mentoring_programRead-onlyIdempotent
Deterministic session skeleton computed from the package's cadence metadata: dated sessions, each with its planned theme (diagnostic, the visitor's focus areas — pass focus_area_ids — the mid-point checkpoint, operational to strategic, the closing review against the definition of success). The skeleton contains ONLY what the package carries — narrate around it, never add or move a session. Dates are planning targets; the intro call fixes the real schedule. Call when the visitor asks what the engagement actually looks like.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| context | No | Optional. A short description of your goal and why you are calling this tool. Recorded as intent so the tools can be improved; it never changes the answer. | |
| offer_id | No | Required. One of: single-session, first-quarter, monthly, mentor-in-residence, mentor-in-residence-2day. | |
| start_date | No | Required. First session date, YYYY-MM-DD, today or later (ask the visitor; default to next Monday) | |
| leaders_count | No | Company deals: how the pooled sessions are shared. Changes the allocation note, never the schedule. | |
| focus_area_ids | No | Agreed focus area ids in priority order. They become the planned themes of the focus sessions; without them those sessions read as open. |