monday-planning

# Monday Planning ## Goal Read last week's training load from `state/strava-weekly-baselines.json` (written by weekly-load-review on Sunday). Generate a concrete weekly training plan suggestion and deliver it via the configured channel. ## Steps 1. Read `state/strava-weekly-baselines.json`. If missing or last entry is not from yesterday (Sunday), call `mcp__strava__get-recent-activities` with `perPage: 20` to compute last week's totals manually. 2. Read last week's totals: run km, run sessions, elevation, strength sessions, bike sessions. 3. Read the 4-week rolling average from the baseline file (or compute from available data). 4. Apply planning logic (see below) to generate a 5–7 day training structure. 5. Send a message via the configured channel. If no channel is configured, pipe the plan into `.claude-code-hermit/bin/hermit-run task note .claude-code-hermit <id>` only inside an open record's turn (otherwise skip the note) instead and skip the notification. Compose in the operator's configured voice, covering the load context, daily structure, and key workout. Example shape: ``` 🗓️ Week plan: [Mon date] Based on last week: [X]km running, [load flag] Suggested structure: Mon: [activity] Tue: [activity] Wed: [activity] Thu: [activity] Fri: [activity] Sat: [activity] Sun: [activity] Key session: [highlight the week's main workout] ``` 6. Write the weekly plan to `.claude-code-hermit/compiled/weekly-plan-<YYYY-MM-DD>.md` (today...