fitness-brief

# Fitness Brief One skill, two lenses on the same athlete's training state. Composition is intent-driven, not scripted: gather a bounded digest, then write the brief toward the goal below in the operator's configured voice — there is no fixed section order, no hardcoded tone, and no mandatory rest-day copy. ## Flags - `--morning`: slot `morning`. Forward-looking. - `--evening`: slot `evening`. Backward-looking. - `--slot <name>`: custom slot label; orientation defaults to forward-looking unless the operator's own conventions say otherwise. Resolve `<slot>` from the flag before starting. Filenames below use that resolved value. Steps below say "Morning"/"Evening" as shorthand for forward-looking/backward-looking orientation — a custom `--slot` follows whichever branch matches its resolved orientation. ## Steps 1. **Connectivity + sync mechanics.** These fold in what `strava-health-check` and `strava-sync` used to run on their own crons — this brief now owns that beat. - Call `mcp__strava__check-strava-connection`. If disconnected: say so plainly in the brief and skip the data-dependent parts below rather than fabricating figures. - **Evening only:** call `mcp__strava__get-recent-activities` (`perPage: 5`), compare against `state/strava-last-activity-id.txt` (treat missing as "none"), and for any new activity whose Strava `type` is `Run`, invoke `/claude-code-fitness-hermit:activity-deep-dive <id>` (cap 3 — log skipped IDs to SHELL.md P...