Workout

**Judgement:** A strong, domain-focused skill for structured strength-training logging and analysis, especially when users already use `workout-cli`. It is well-suited for recording gym sessions, managing multiple users, and querying PRs/volume/progression. **Key strengths** - Multi-user profile support with shared exercises but per-user data fits real-world household/coach scenarios. - Commands cover the full workflow: starting/finishing sessions, logging/editing sets, managing exercises/templates, and querying history and PRs. - Emphasis on data integrity (must add exercises first, must log real weight/reps, notes as metadata only) aligns with reliable analytics. - `--json` support on all commands makes it straightforward to integrate into assistant workflows for structured reading and summarization. **Main risks / failure modes** - If the assistant forgets to **add a new exercise before logging it**, log commands will fail; this is a critical requirement. - If the assistant logs **0 lbs** or guesses weights/reps instead of asking the user, it corrupts progression and PR data; the tool assumes accurate numbers. - Multi-profile setups require the assistant to correctly specify `--profile` to avoid mixing users’ histories. - Weights are in **lbs only**, so unit confusion is possible for users who think in kilograms unless the assistant clarifies and converts. **Recommended scenarios** - Users explicitly asking to *record* or *update* their gym workouts, track sets, or maintain consistency across sessions. - Users wanting summaries of recent training, progression on a specific lift, weekly volume, or personal records. - Multi-user or coach/client contexts where each person’s training history must stay separate but share a common exercise library. - Any assistant workflow that benefits from structured, queryable workout history rather than free-form text notes.