/today — Morning Briefing

1. Get today's date. Read

   knowledge/recovery-overtraining.md

   for overtraining warning signs and

   knowledge/workout-types.md

   for workout execution guidance.
2. Fetch data using MCP tools (call them directly, in parallel where possible):
   • Events endpoint for the next 14 days (oldest=today, newest=today+13) — today's workout plus the full training block ahead for context
   • Wellness endpoint for the last 3 days (oldest=today-2, newest=today) — trend context, not just a snapshot
   • Fitness endpoint for the last 7 days to show trend
   • Weather endpoint using the athlete's lat/lon from their profile — current conditions and forecast
   • Zones are cached in

     athlete/profile.md

     — skip the athlete endpoint unless the zones section is missing
3. Display:
   • Today's Workout: Name, type, planned distance/duration. If the workout has structured steps, show target zones/paces using the athlete's actual zone values. If rest day, say so.
   • This Week / Next Week: Brief overview of the 2-week plan ahead — session names, days, types. Highlight the training block context (build week? recovery week? race week?) so today's workout makes sense in the bigger picture.
   • Wellness: Sleep, HRV, resting HR, fatigue, mood (whatever is available)
   • Form Status: Current TSB with label (fresh/neutral/tired/fatigued)
   • CTL/ATL: Current values and 7-day trend direction
   • Weather: Current conditions and today's forecast (temp, feels-like, wind, precipitation, UV). Flag heat/cold/rain concerns that affect the workout — suggest timing adjustments, hydration, or gear.
4. Check data freshness. Look at today's wellness

   updated

   timestamp. If it's more than 1 hour old (or missing entirely), warn the athlete that their device may not have synced recently — wellness and fitness numbers may be stale. Suggest they open Garmin Connect (or their watch app) to trigger a sync, then ask you to re-run

   /today

   . Keep the warning brief: one line, not a blocker.
5. End with a one-line recommendation grounded in the knowledge base (e.g., reference workout purpose from

   knowledge/workout-types.md

   , or flag recovery concerns per

   knowledge/recovery-overtraining.md

   )
6. Flag any injury risk signals (volume spike, sustained negative TSB, poor sleep) using criteria from

   knowledge/injury-prevention.md