Schedule an advanced set in your routine

You like rest-pause on the last set of bench but you don't want to think about it every Monday — you want it built into the routine. You tell the agent to add bench-press-as-rest-pause to push day, and from then on the planned queue carries the cluster shape ready to log.

What the agent needs to hear

Behind your sentence, the agent works backwards to four pieces: which routine day, the advanced set type — rest-pause, drop set, superset, pyramid, AMRAP, or giant set — the exercise (or exercises, for supersets and giants), and the target structure that gives the cluster its shape. For rest-pause that’s the working weight plus the rep sequence; for drop sets it’s the stage drops; for supersets and giants it’s the rounds and target reps.

Day comes from your active routine by default — « push day » resolves cleanly if your routine has one. The type defines the rest. If you’re editing a different routine, name it: « add it to push day in PPL v2 ». Name the variation when the catalog is ambiguous.

Type-specific defaults

Each advanced set type has its own default shape, and you override in the same sentence. Rest-pause assumes 3 mini-sets at the same working weight; you give the rep sequence (« 1-4-2 »). Drop set defaults to 3 stages descending — 20% per stage unless you specify (« 3 stages from 60, dropping 10 each »).

Superset assumes 2 exercises, same target reps, 3 rounds. Pyramid climbs 3 steps by default; name the rep and weight curve (« 10-8-6 at 80-90-100 »). AMRAP is a single set at a named weight, max reps as outcome. Giant set runs 3 or more exercises, target reps, 3 rounds. Any default bends to a number you say out loud.

Template-side vs session-side

This recipe edits the routine template, not the live session. Once scheduled, the planned advanced set shows up in the day’s queue every time you run it — bench with a rest-pause cluster baked in, lat pulldown with the drop set already shaped. The logging recipes — rest-pause-set, log-a-drop-set — still apply to capture what you actually did, including deviations from the plan.

Past sessions of this day don’t get retroactively rewritten. Your history reflects what you trained; the template change is forward-looking. From the next session onward, the queue carries the cluster shape and the logging step is just confirming the actuals.

When the agent gets it wrong

Three failure modes show up. Wrong type applied — you said rest-pause and the agent shaped it as a drop set. Correct it by naming the contrast: « no, rest-pause — same weight across, not descending ». Wrong exercise attached, especially on supersets and giants where you named two or three: « curls and tricep extensions, not curls and chest flys ». The card swaps the wrong one in place.

Targets that don’t match the type’s structure are the subtle one. You said « 1-4-2 » for a drop set — that’s a rest-pause rep shape, not descending stages. Either rename the type or restate the targets in the shape the type expects.

What makes the scheduled advanced set worth keeping

Three things decide whether this scheduled advanced set lands cleanly: the type matches the training intent (rest-pause for intensity holds, drop set for volume past failure, superset for density — pick the type that matches the block goal), the exercise is loadable for that type (rest-pause on a heavy compound is reasonable; on dumbbell flys it’s awkward — type and exercise have to fit), and the targets match the type’s shape (rep counts in the order the type prescribes — descending for drop sets, equal for rest-pause across). Scheduling the cluster at the template level removes the decision from every session and turns logging into confirmation.