references/program-design.md

# Program Design Checklist

Use this reference when drafting a new client workout or multi-week program.

## Select the Stored Object

- One reusable session: `create_workout_template`.
- Multi-week scheduled program: `create_workout_plan_template`.
- Active client assignment: `assign_workout_plan` after the template exists and only when explicitly requested.

## Required Inputs

Obtain or confirm:

- client;
- goal;
- experience;
- sessions per week;
- session duration;
- available equipment;
- movement constraints or exercises to avoid;
- requested start or assignment intent.

Ask only for missing information. Do not request diagnoses or medical records.

## Construction Checklist

- Give each workout a clear name and purpose.
- Keep exercise order coherent: preparation, primary work, supporting work, optional conditioning or cooldown.
- Match set fields to the exercise measurement type.
- State rest guidance and progression assumptions in the trainer-facing draft.
- Keep weekly demands plausible for the stated experience, frequency, and session duration.
- Avoid unnecessary novelty and duplicate movement patterns unless the trainer requested them.
- Use exercise ids returned by `list_exercises` or `list_official_exercises`.
- Preserve the units returned or explicitly selected by the trainer.

## Tool Data Rules

- A workout exercise entry must reference a verified exercise id.
- Use `week` and `day` as zero-based values when building plan workouts.
- Use `time: custom` only with a valid `customTime`.
- Include the complete intended exercise list in every created workout.
- Do not claim assignment until `assign_workout_plan` succeeds.

## Trainer Draft

Before writing, show:

1. program objective;
2. schedule;
3. session names;
4. ordered exercises and sets;
5. progression assumptions;
6. unresolved constraints;
7. whether the next action saves only or also assigns the plan.