Update to Lifterly

{
  "description": "Plan the user's training in Lifterly over any span (the next days, a week, a month, a program), one session per training day matching their weekly goal and split, around what is already planned, and add the sessions once they agree. Use when the user asks to plan their week, the next days, a month, a training schedule or a program.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 377
    },
    {
      "relative_path": "references/programming.md",
      "size_in_bytes": 2869
    }
  ],
  "name": "plan-training",
  "skill_md_contents": "---\nname: plan-training\ndescription: Plan the user's training in Lifterly over any span (the next days, a week, a month, a program), one session per training day matching their weekly goal and split, around what is already planned, and add the sessions once they agree. Use when the user asks to plan their week, the next days, a month, a training schedule or a program.\n---\n\n# Plan training\n\nThe user's explicit instructions (span, days, times, split, number of\nsessions) always win over these defaults. Without a span, plan the coming\nweek.\n\n\"Plan my week\" asks for a proposal, not for saved sessions: always show the\nplan in a `show_plan_proposal` card first, and add nothing until the user\nagrees or adds it with the card's button.\n\n## Gather\n\n1. `get_training_profile`: goal, level, equipment, `workoutsPerWeekGoal`,\n   weight unit.\n2. `list_planned_workouts` for the span: keep what is already planned, and\n   only fill the remaining days unless the user asks to replace them.\n3. `list_workouts` for the last two weeks: what they trained and how often.\n4. Settle the days and times. Ask once, in a single question, if the user did\n   not say which days or what time they train; do not invent a schedule.\n\n## Choose the split\n\n- 1–2 sessions a week: `fullBody`.\n- 3 sessions: `fullBody`, or `ppl` (push, pull, legs).\n- 4 sessions: `upperLowerSplit` (upper, lower, upper, lower).\n- 5–6 sessions: `ppl` twice, or `arnoldSplit`.\n- Keep the split the user already follows when their history shows one.\n- Leave at least a day between sessions that load the same muscles.\n\n## Build each session\n\nFor each day: `search_exercises` with its `workoutType` and `splitPart`, then\n`get_exercise_progress` for the candidates, and apply\n[references/programming.md](references/programming.md). Vary exercises between\nsessions of the same part.\n\nOver several weeks, progress the main lifts gradually from week to week (a\nsmall weight or rep increase on the previous week's targets, more slowly for\nadvanced lifters), and plan a lighter week after every three to five hard ones\nwhen the span allows it.\n\n## Long programs\n\nA card and an answer have limits: propose at most about four weeks of\nsessions at once. For a longer program, agree on its structure first (split,\nweekly progression, lighter weeks), then propose it in blocks of up to four\nweeks, one block per answer, continuing from where the last block ended.\n\n## Show and confirm\n\n1. Call `show_plan_proposal` once with every session of the span or block\n   (each the plan `create_planned_workout` would save, `plannedAt` in the\n   user's time zone, ISO 8601 with its offset). It shows them in one card,\n   by week, each session opening to its exercises, with an \"Add all to my\n   plan\" button. Never call `show_workout_proposal` once per session:\n   ChatGPT keeps only the last card of an answer.\n2. Summarize the plan in a few lines (days, sessions, why this split, how it\n   progresses) and ask the user to confirm it.\n3. If they ask for changes, adjust and call `show_plan_proposal` again.\n4. When they agree in the conversation, call `create_planned_workouts` once\n   with all the sessions (unless they already added them with the button:\n   the tool result or the card says so), then `show_week_plan` for the first\n   week.\n\nIf sessions are refused, fix what the result says for those only and add\nthem again; tell the user if a session could not be added.\n"
}