Fitness Tracking & Progress Review

⚠️ Educational only. This skill does not replace a certified coach, sports scientist, or medical professional. It does not interpret medical data or diagnose conditions from workout metrics. Interpretation of data is educational and suggestive, not prescriptive. This skill encourages subjective feeling alongside objective data. The user makes all training decisions. If you experience persistent fatigue, pain, or concerning symptoms, consult a healthcare professional.

Description

Helps the user interpret their fitness data from apps, logs, or journals to assess progress and adjust training. Provides a structured review framework that combines objective metrics with subjective feel to make informed training decisions.

When to Use

This skill applies when the user wants to:

• Review a block of training (2-8 weeks) to assess what worked and what didn't
• Identify trends in performance, consistency, or fatigue
• Diagnose why progress has stalled or plateaued
• Make data-informed adjustments to the next training block
• Integrate subjective feedback (energy, mood, soreness) with objective data

Required Inputs

To perform a meaningful review, the skill needs:

• Training log or data — workout records, distances, times, weights, heart rate, or perceived exertion
• Original goals — what the user was aiming for during this period
• Time period being reviewed — start and end dates of the training block
• Subjective feel and energy levels — how the user felt during training, daily energy, sleep quality
• Any observations or concerns — anything the user noticed, questioned, or worried about

If the user doesn't have formal tracking data, work with what they do have: memory, calendar entries, app screenshots, or a verbal summary.

Prompt Flow

1. Review the user's training log or data for the review period.

   • Ask the user to share whatever data they have in whatever format.
   • Help extract key patterns: frequency, volume, intensity, consistency.
   • Let the user describe their data before offering analysis.

2. Compare outcomes against original goals and expectations.

   • Did the user achieve what they set out to? Partially? Exceeded?
   • If goals weren't met, explore gap without blame — is the gap in execution, goal realism, or measurement?
   • Celebrate wins, even small ones. Progress is not all-or-nothing.

3. Identify trends, plateaus, and areas of improvement.

   • Look for patterns: consistent weeks vs. chaotic weeks, progression vs. stagnation, rising vs. falling energy.
   • Distinguish between a true plateau and a temporary stabilization before the next adaptation.
   • Flag if consistency was the main driver of results (or lack of results).

4. Suggest training adjustments based on observed patterns.

   • If progress stalled: consider volume adjustment, deload, or changing stimulus.
   • If consistency was low: address scheduling, motivation, or life-load issues.
   • If fatigue is rising: reduce volume, increase recovery, check sleep and nutrition.
   • Always err conservative — suggest one change at a time.

5. Help set goals for the next training cycle.

   • Use insights from the review to inform realistic next-cycle goals.
   • Recommend keeping what worked, adjusting what didn't, and introducing at most one new variable.
   • Set a next review date to maintain accountability.

Output Structure

1. Progress summary against original goals — what was achieved, partially achieved, or not achieved
2. Trend identification — at least two observed patterns with supporting context
3. Plateau or regression flags — areas where progress stalled or declined with possible explanations
4. Training adjustment suggestions — at least three specific, actionable changes for the next cycle
5. Next cycle goals and focus areas — recommended targets based on review insights

Safety Boundaries

• Does not replace a certified coach, sports scientist, or medical professional.
• Does not interpret medical data or diagnose conditions from workout metrics.
• Interpretation of data is educational and suggestive, not prescriptive.
• Encourages subjective feeling alongside objective data — data is a tool, not the truth.
• Avoids creating anxiety around metrics or promoting obsessive tracking.
• The user makes all training decisions.
• If data suggests possible overtraining syndrome, significant performance decline with no clear cause, or concerning physiological signals, recommend professional assessment.