plan-workout9.93 KB
View saved version →
---
name: plan-workout
description: Plan, schedule, or change a MoveMate workout — a session for a given day, a superset or circuit, a saved workout ("My workouts") created or edited, or an edit to one already on the schedule. Reads recent training, picks real exercises from the user's library, proposes the session, and writes only after the user agrees. Not for reporting on past training — use review-training for that.
---
# Plan a workout in MoveMate
Scheduling writes to the user's real training calendar. Propose first, write once, and never invent an ID or a number.
## 1. Read before you plan
Call these first — planning without them produces a session that ignores what the user actually does:
- `get_training_stats` (`period`: `last_7d` | `last_30d` | `last_90d` | `last_year` | `all_time`) — volume, frequency, streak, and which muscle groups are already covered this week.
- `get_recent_workouts` — what the user actually managed last time, set by set. Build the next session on these numbers: add reps or a set to what they completed, not to what was on paper. Narrow with `exercise_name` to see one movement across its last few sessions, and check `completed_sets` against `planned_sets` before repeating a target they already missed. For bodyweight work this is the only source of the number that matters — total reps.
- `list_planned_workouts` — what is already scheduled. **Never put a second workout on a day that already has one** unless the user explicitly asks for two.
- `get_body_profile` — height, weight, age, fitness level, goals, available equipment. Takes no arguments.
- `get_personal_records` — only when the user's request is about pushing a specific lift.
If the user named a day, resolve it against their timezone (`get_profile` returns it), not yours.
## 2. Pick real exercises
Every `exercise_id` must come from `search_exercises` (`query` or `queries`, `muscle_group`, `equipment`, `limit`) or from `create_custom_exercise`. Look up all the exercises of a session in one call — pass their names together in `queries` — rather than one call per exercise. `search_exercises` shows the user nothing; use `show_exercises` only when the user asks to see exercise options. **Never write an ID from memory, and do not carry one over from an earlier conversation** — look it up again. Custom exercises in particular exist only for the user who created them.
If nothing in the library matches what the user described, create it with `create_custom_exercise` (`name`, optional `muscle_group`, `equipment`, `notes`) rather than substituting a different movement silently. If you do substitute, say so.
Respect the equipment in `get_body_profile`. Do not program a barbell session for someone who has dumbbells only.
## 3. Weights, reps and units
- `target_weight` is **always kilograms**. If the user speaks in pounds, convert (`lb / 2.20462`) before sending, and keep speaking pounds back to them.
- Base loads on `get_recent_workouts`, `get_exercise_progression` or `get_personal_records` for that exercise. A weight far above the user's history is rejected: the server clamps anything over 3× their last known weight and returns a warning.
- For an unloaded movement, progress the **reps**, not the weight: send `target_reps` per set and leave `target_weight` off entirely rather than inventing a load.
- Limits: at most 15 exercises per workout, at most 10 sets per exercise, and the date must be within 120 days.
- Label sets with `set_type` when they are not plain working sets. `"warmup"` for preparatory sets, `"failure"` for a set meant to be taken to failure, `"drop"` for a set at a reduced load immediately following another. The default is `"normal"` and can be left off. Warm-ups and drop sets are excluded from volume, effort averages and the weight progression, so labelling them correctly is what keeps the user's numbers honest. (`is_warmup: true` still works but is deprecated — prefer `set_type: "warmup"`.)
## 4. Supersets and circuits
A Preview of the first 4,000 characters. Read full instructions →
review-training4.45 KB
View saved version →
---
name: review-training
description: Report how the user's MoveMate training is going — weekly or monthly summaries, whether a lift is progressing or stalled, plateau diagnosis, and personal records. Read-only: it never schedules or changes anything. Not for planning or editing a session — use plan-workout for that.
---
# Review training in MoveMate
Every number in the answer must come from a tool result. This skill only reads.
## Pick the right tool
- **"How did I do?" / "How was that workout?"** → `get_recent_workouts` with `limit: 1`. This is the only tool that returns individual sets — reps and weight of every completed set, `reps_per_set`, `total_reps`, and the planned targets the user was working against. Use it whenever the question is about a specific session rather than a period.
- **"How was my week/month?"** → `get_training_stats` with `period` (`last_7d`, `last_30d`, `last_90d`, `last_year`, `all_time`) and optional `muscle_group`. Returns volume, frequency, streak and weekday distribution.
- **"Why has my bench stalled?" / "Am I getting stronger on X?"** → `get_exercise_progression` with `exercise_name` (or `exercise_id` if you have a real one from `search_exercises`) and optional `period`. It returns the per-session trend plus `trend` and `plateau_weeks` — use those fields rather than eyeballing the series yourself. `progression_metric` tells you which series they were computed from: `estimated_1rm` for a loaded lift, `total_reps` for a bodyweight one. Report progress in those same terms.
- **"How does that compare to last time?"** → `get_recent_workouts` with `exercise_name` and `limit` up to 10, which returns that movement's sets across its last few sessions. Prefer this over `get_exercise_progression` when the comparison is about reps or sets rather than load.
- **"What are my PRs?"** → `get_personal_records`, optionally narrowed by `exercise_id`, with `limit` up to 100.
- **"Did I finish what was planned?"** → `get_recent_workouts`. Compare `completed_sets` against `planned_sets` and `total_reps` against `planned_total_reps`. Sessions logged ad-hoc have `from_plan: false` and no targets — say there was no plan to compare against rather than treating what they did as the plan.
- Anything about the person rather than the training (timezone, how long they have been a member, average sessions per week) → `get_profile`. Body stats and goals → `get_body_profile`.
For a plateau question, read the progression **before** offering an explanation. A stall of two weeks and a stall of three months call for different answers.
## Bodyweight movements
For pull-ups, push-ups, dips, bodyweight squats and anything else done unloaded, **total reps and reps per set are the result** — `total_volume_kg` and `estimated_1rm` are 0 and mean nothing there. Use `get_recent_workouts` and talk in sets and reps: "24 total pull-ups across 5 sets (4, 5, 6, 5, 4)". Progress is more reps at the same set count, more sets at the same reps, or the same total with fewer sets — say which one you are looking at.
## How to report
Lead with the answer in one or two sentences, then the few numbers that support it. A wall of every returned field is not a review.
Give at most one concrete adjustment, tied to what the data shows — a load change, a frequency change, a rep-range change. Say what you would expect to see if it worked.
State the period you are describing. "Your volume is up" is meaningless without "over the last 30 days".
## Honesty rules
- If a tool returns nothing — no sessions in the period, no history for that exercise — say so directly. Never fill a gap with a plausible number, an estimate, or an example.
- Do not claim a trend the data does not support. Two sessions is not a trend.
- Distinguish what was **planned** from what was **completed**. Stats and records come from completed workouts; a scheduled session the user skipped is not training that happened.
- The user's own numbers are the reference point. Do not compare t
Preview of the first 4,000 characters. Read full instructions →