reviewlisted

# /review — Post-Workout Analysis 1. Get today's date. Read `knowledge/workout-types.md` to understand the purpose and targets of the workout type being reviewed. For long runs, also read `knowledge/long-runs.md`. For intervals, also read `knowledge/aerobic-base.md`. 2. Fetch data using MCP tools (call them directly, in parallel where possible): - Intervals.icu activities endpoint for the last 3 days, if configured; otherwise Strava activities for the same period - Intervals.icu events endpoint for the last 3 days when available, to find a matching planned workout - If both providers report the same session, treat it as one physical activity, not two workouts. 3. Identify the most recent activity and fetch its details. Use Intervals.icu interval data where available; use Strava detail for athlete-authored notes, perceived exertion, and gear when relevant. Do not fetch Strava comments unless the athlete asks about them. 4. Display: - **Workout Summary:** Name, type, date - **Planned vs Actual table:** | Metric | Planned | Actual | Diff | |--------|---------|--------|------| | Distance (mi) | | | | | Duration | | | | | Avg Pace (min/mi) | | | | | Elevation (ft) | | | | - **Heart Rate:** Avg, max, time in zones (if available) - **Cadence:** Avg (if available) - **Intervals/Laps:** Key splits if interval data exists - **Training Load:** load/TSS from the activity 5. If the activity warrants deeper analysis (tempo runs, int