The Sparse-Plan Nudge
When you hit Save and one-or-more days look light on exercises, BuildStability surfaces a non-blocking yellow notice above the Save bar with two action buttons. It's a friendly check, not a hard block.
When the nudge fires:
• Any day in the template has between 1 and 3 populated exercises • AND the day's name isn't a deliberate-low-volume convention: *Rest*, *Active Recovery*, *Mobility*, *Stretching*, *Off*, *Deload*
Why those exclusions: trainers commonly schedule a 1-2 exercise day on purpose for recovery / mobility / deload work. Naming the day with one of those keywords tells BuildStability to leave it alone.
The two action buttons:
[Ask Repley to fill] — opens the AI chat sidebar pre-loaded with a prompt like *"Add 4–5 more exercises to Week 1's Day 3 of {template name} matching the existing pattern."* Repley reads the day's other exercises and suggests complementary additions in under 15 seconds. The notice closes; you save manually after Repley fills the gap.
[Save anyway] — saves the template as-is. After this, the nudge will NOT re-fire on subsequent saves of the same template — you've made an informed call once. The dismissal is per-template + per-browser (localStorage), so opening the same template on a different device shows the nudge again the first time.
[X / Keep editing] — close the notice without saving. Useful when you realise you wanted to add the missing exercises yourself before saving. The nudge will re-fire on your next save attempt unless the days reach the threshold or you "Save anyway".
The threshold (4 exercises) is opinionated, not magical:
Most strength days have 5–8 exercises. 4 is the bottom of "looks complete" for a typical session. The threshold doesn't account for: • EMOM / AMRAP days that are intentionally one prescription block (a single `EMOM 20` exercise is the whole workout) • Sport-specific days like a single 10K run
For those cases, name the day to match the pattern (e.g. "EMOM Conditioning") or use *Active Recovery* / *Off* — or just hit Save anyway. We'd rather a couple of false-positive nudges than miss a genuinely half-built day.
Why this matters:
The nudge exists because half-finished templates are the silent failure mode of manual programming. Trainers come back to a template, see "Day 3 — 1 exercise" and remember they got distracted mid-build. The nudge catches it at save-time so it never ends up in front of a client like that.