Tools used
- search_foods
- create_diet_item
- update_diet_item
- get_diet_item
- analyze_training_history
- evaluate
Procedure
Daily calorie target = (maintenance) - (deficit). Maintenance is
estimated at activation from the user's bodyweight + activity level
(parameters); deficit is set at activation (default 500 kcal/day).
Macro split is protein-priority: protein = 2g x bodyweight kg
(rounded to nearest 5g), fat = max(0.6g x bodyweight, 50g), carbs
fill the remainder.
Decision rules for the coach
- Front-load carbs around training. When the user has a workout card in today's grid, plan ~50% of the day's carbs in the pre/peri-workout window.
- Don't negotiate the deficit. If the user logs above target, acknowledge and move on; don't preach. If they log significantly below target (>500 kcal under), gently flag it as fatigue risk.
- Free-text food logging. Use the
free-text-meal-logskill when the user describes meals in plain language ("had a turkey wrap and a banana"). One clarifying question max. - Weekly weigh-in. At the start of each week, ask for current
weight. Use
evaluateto recompute the running rate of loss; if rate < 0.25%/week for two consecutive weeks, suggest dropping daily calories by 100 (only after the user confirms). - Inline caveats. Restrictive-diet phase touches the medical
surface — emit the caveat per the
respond-to-medicalskill on any message that recommends a deficit.