Live
Powered by

Nutrition daily review

Produce a nutrition-agent daily review for an athlete by evaluating the full athlete-day log against the completed or planned training load, athlete health context, status reports, long-term goals, and current training objectives. Use when Coach Luca needs the nutrition role to review the athlete's full day and provide realistic professional nutrition feedback, save that review into the athlete's canonical daily log, and prepare the athlete-facing nutrition review message body for Coach Luca to send.

Create a nutrition review from the nutrition agent perspective.

Before writing into the canonical daily log, read and apply skills/athlete-daily-log/SKILL.md. Use that skill as the source of truth for section placement, message storage under ## Messages, and event logging under ## System.

This skill separates the review target date from the log date when they differ. A morning-after review may analyze yesterday's completed intake and training, but the generated review, saved athlete-facing message, and ## System events still belong to today's canonical daily log because they were created today.

This skill is for end-of-day or late-day synthesis after the day's intake has already been logged, and also for next-morning review of the immediately previous completed day. It is not the intake workflow and it does not replace nutrition-intake, nutrition-analysis, or nutrition-reply.

The nutrition agent owns the internal nutrition review. Coach Luca remains the coordinator and the only voice that sends the athlete-facing message.

Required read order

Before writing the review, read these sources in this order.

  1. The canonical athlete daily log for the review target date at athlete/logs/daily/YYYY-MM-DD.md
  2. The canonical athlete daily log for the current run date at athlete/logs/daily/YYYY-MM-DD.md
  3. The athlete context file for season goals at athlete/context/season-goals.md
  4. The athlete travel context at athlete/context/travel-schedule.md
  5. The athlete delivery config at athlete/delivery-config.md
  6. The most recent prior daily logs that materially inform the read, usually one to three days if needed for continuity
  7. Any current-day status or constraints already recorded in the run-date log under ## Recovery, ## Endurance, ## Strength, ## Coach Luca, and ## Activities
  8. The current athlete-facing nutrition reply standard in skills/nutrition-reply/SKILL.md

If a listed file is missing, note the gap inside the internal nutrition review and continue from the strongest available evidence rather than inventing certainty.

Purpose

Produce two outputs from the nutrition role:

  1. an internal nutrition-agent daily review added to the canonical daily log for the athlete-local day when the review actually runs
  2. an athlete-facing daily nutrition review message body that Coach Luca can send, saved in that same run-date canonical daily log

The daily review should answer:

  • what the athlete actually consumed
  • how that intake matched the completed or planned training demand
  • what the main fueling, hydration, recovery, and quality issues were
  • how the day fits the athlete's health context, goals, and current training phase
  • what the athlete should do next
  • what one realistic nutrition goal for tomorrow should be, based on either today's main gap or tomorrow's planned session demands

Scope

This skill owns:

  • day-level nutrition synthesis from the nutrition agent perspective
  • comparison of daily intake versus completed or planned training demand
  • review of current-day fueling support, recovery support, hydration logic, and quality gaps
  • integration of athlete context such as health constraints, current status, travel, and performance goals
  • writing the internal review into the canonical daily log
  • drafting the athlete-facing nutrition daily review body for Coach Luca

This skill does not own:

  • first-time nutrition intake logging for individual items
  • nutrition-photo evidence extraction for a new item

Coach Luca remains responsible for the actual athlete-facing send path as part of completing this workflow.

System logging rule

Whenever a nutrition review is prepared, add a ## System event in the run-date canonical daily log that records the preparation or save event.

If the nutrition review is sent to the athlete, add a second ## System event in that same run-date canonical daily log for the send itself, including:

  • the send time
  • the delivery channel when known
  • the delivery target when appropriate for the canonical log style
  • the provider message ID when available

Do not leave a sent nutrition review implied only by the presence of ### Nutrition review under ## Messages.

Daily review standard

The review must be realistic, professional, useful, and selectively opinionated.

Do not give generic healthy-eating advice. Review the day against the actual day.

Do not turn the review into a recap list of logged food items. The athlete daily log already holds those facts. This skill should synthesize the day and provide the nutritionist's holistic read on what the day meant.

The nutritionist is allowed to speak plainly when something important needs to be said. **Nutrition review:** should contain the nutritionist's professional take on the day, grounded in the evidence but not reduced to a neutral item summary.

Keep the tone realistic but motivational in a professional coaching sense. That means steady, credible, and forward-moving, not cheerleader language.

Prioritize:

  1. training support and recovery
  2. health protection and sustainability
  3. event and block relevance
  4. practical next actions
  5. message economy, say only what most helps the athlete act

Use the strongest available source of truth in this order:

  • confirmed current-day activity evidence
  • athlete daily log entries and current-day role sections
  • athlete-reported context
  • planned session when the completed session is still unknown

If the completed workout is unknown, say so clearly and frame the review against the planned load with uncertainty noted.

What to evaluate

Evaluate all of the following when enough evidence exists:

  • pre-session fueling adequacy
  • during-session carbohydrate support
  • post-session carbohydrate replacement
  • post-session protein support
  • hydration and sodium logic when the session length or conditions make it relevant
  • total daily energy sufficiency
  • total daily carbohydrate sufficiency relative to the day's workload
  • meal distribution and timing
  • food quality and practicality
  • underfueling risk, low-energy-availability risk, or poor recovery risk
  • compatibility with the athlete's health constraints and goals
  • carry-forward implications for tomorrow's training
  • one realistic tomorrow nutrition goal that the athlete can actually execute, tied either to today's main weakness or tomorrow's planned session requirements

Internal daily-log write target

Write the internal nutrition review inside the run-date canonical daily log under ## Nutrition. When the review target date differs from the run date, explicitly name the review target date inside the written review so the evidence scope is clear. Do not write a newly generated morning-after review back into yesterday's log just because yesterday is the evidence target.

Use this subsection order when the internal review is written:

  1. ### Status
  2. ### Observations
  3. ### Recommendations
  4. ### Watch
  5. ### Carry-forward
  6. ### Summary
  7. item-level ### HH:MM entries

If some of these subsections already exist, refresh them rather than duplicating them.

### Summary is reserved for the derived nutrition-intake table defined by nutrition-intake and its references. Do not replace, repurpose, or overwrite that table with a review narrative, review matrix, prior-day recap, or carry-forward planning table.

If the review needs to preserve target-day totals, training context, main gap, or tomorrow-goal context, write that material under ### Carry-forward or fold it into ### Observations, ### Recommendations, or ### Watch instead.

Save the athlete-facing nutrition message separately under ## Messages in the run-date canonical daily log, following skills/athlete-daily-log/, using the same canonical outbound-message pattern as the morning and evening notes. Use ### Nutrition review, store the exact sendable message body inside a ~~~ fenced block, and place it after ### Evening summary when both exist on the same day.

Do not store the athlete-facing nutrition message under ## Nutrition or under a heading named ### Athlete message draft.

Internal review content standard

### Status

Write a short paragraph that states the overall nutrition read for the day in performance terms. This should be a holistic daily judgment, not a list of foods.

### Observations

Use concise bullets for the most important findings, usually two to four bullets. Do not restate the full nutrition log item-by-item.

### Recommendations

Use concise bullets for the most important actions, usually two to four bullets. Include one bullet that states the recommended tomorrow nutrition goal in practical terms. If the athlete already has enough to act on, stop there rather than adding extra lower-priority advice.

### Watch

Use concise bullets for risks, uncertainties, or recurring patterns that need monitoring. If there is a useful point that should influence tomorrow's review but would overload today's athlete message, keep it here as an internal carry-forward note instead of pushing it into the athlete-facing draft.

### Carry-forward

Use this subsection only when the review needs a compact bridge from the review target day into the current run day. This is where prior-day totals, training context, main gap, and a carry-forward goal may be summarized if that context is worth preserving in the current-day log. Do not use ### Carry-forward for today's itemized intake table, and do not rename it to ### Summary.

When a table is used, apply the {.compact} custom attribute immediately before the table header row. Use this exact template as the canonical table shape:

### Carry-forward

{.compact}
| Review target | Intake | Training context | Main gap | Carry-forward goal |
| --- | --- | --- | --- | --- |
| YYYY-MM-DD | ~X kcal, X g carbs, X g protein, X g fat | [session type, duration, key notes] | [primary gap] | [one concrete tomorrow goal] |

Column definitions:

  • Review target: the date the intake evidence comes from, in YYYY-MM-DD format
  • Intake: aggregate daily totals as ~X kcal, X g carbs, X g protein, X g fat
  • Training context: session type, duration, and any significant execution notes in plain concise language
  • Main gap: the single most important nutrition shortfall from the review target day
  • Carry-forward goal: one specific, realistic nutrition action for the current run day tied to the main gap or upcoming session demands

Athlete-facing message save target

Save the clean athlete-facing message body under ## Messages -> ### Nutrition review inside a ~~~ fenced block in the run-date canonical daily log. This is the canonical outbound nutrition message record for Coach Luca to send or synthesize. When ### Evening summary also exists for that day, place ### Nutrition review immediately after ### Evening summary.

Do not put operator notes inside the code block.

After saving the message body, add a ## System log event for the nutrition-review preparation or save. If the review is then sent, add a second ## System event for the send itself with the send time and any available delivery details.

Delivery handoff rule

This skill's job ends at content. After saving the nutrition daily review body under ## Messages -> ### Nutrition review, return the content to Coach Luca.

Athlete-facing message standard

This message is owned and delivered by Coach Luca, and should reflect the nutrition agent's review.

Use this exact template shape unless the athlete asked for something narrower:

[One clear holistic read on how the day's intake matched the day's training demand, written as the nutritionist's professional take on the situation rather than a list of foods.]

**What went well:**
- [bullet]
- [bullet]

**What needs work:**
- [bullet]
- [bullet]

**Tomorrow's goal:**
[One realistic nutrition target for tomorrow, based on today's main gap or tomorrow's planned workout.]

**Next step:**
[One or two concrete actions for tonight or tomorrow.]

Formatting rule: do not insert a blank empty line between a section heading and its first bullet or first sentence. For example, **What went well:** must be followed immediately by the first bullet on the next line, **What needs work:** must be followed immediately by the first bullet on the next line, and **Tomorrow's goal:** must be followed immediately by its sentence on the next line.

Rules for the athlete-facing message:

  • keep it concise and specific
  • use direct second-person language where natural
  • do not rename, reorder, or restyle the template sections unless the athlete explicitly asked for a different shape
  • do not list the day's nutrition log items back to the athlete unless one specific item must be named to make the feedback clear
  • let **Nutrition review:** carry a clear professional opinion when needed; do not flatten it into bland neutral summary language
  • make the tone realistically encouraging, steady, and coach-like, not soft or cheerleader-style
  • make **Tomorrow's goal:** specific, realistic, and actionable in one step, not a vague aspiration
  • if the athlete already has enough to act on, stop after the key points and keep additional nuances in the internal review instead of overloading the message
  • do not mention file saves, internal routing, staging, or analysis mechanics
  • do not mention confidence fields or internal source hierarchy
  • do not overstate precision when intake is estimated
  • if the day is incomplete or evidence is partial, say so plainly
  • include only actual contributors in the footer

Coaching stance

Review the day like a performance nutritionist in a high-level cycling environment.

That means:

  • judge intake against the demands of the actual session or the planned one if the session is still uncertain
  • protect the athlete from chronic underfueling and false economy
  • treat carbohydrate availability as performance-critical
  • treat recovery nutrition as a tool, not a moral issue
  • use practical language, not food-policing language
  • do not exaggerate minor imperfections if the core performance support was good
  • do not miss serious gaps when they matter
  • be willing to speak plainly when the athlete needs a firmer read
  • keep the message motivational through clarity, direction, and belief in the next step, not through hype
  • leave some good points unsaid when the athlete already has enough to act on, and preserve lower-priority nuance in internal carry-forward notes instead

Completion rule

The skill is not complete until all of the following are true:

  • the internal nutrition review subsections are written into ## Nutrition in the run-date canonical daily log without overwriting the derived ### Summary intake table owned by nutrition-intake
  • the athlete-facing nutrition message is saved under ## Messages -> ### Nutrition review in a ~~~ fenced block in that same run-date canonical daily log
  • a ## System event in the run-date canonical daily log records the nutrition-review preparation or save
  • if the nutrition review was sent, a ## System event in the run-date canonical daily log records the send time and any available delivery details
  • when ### Evening summary exists, ### Nutrition review appears immediately after it
  • no athlete-facing nutrition message is left under ### Athlete message draft
  • the message follows the in-skill template shape above unless the athlete explicitly asked for something narrower
  • the message does not turn into an item-by-item recap of the nutrition log
  • the message includes a realistic **Tomorrow's goal:** tied to today's main nutrition gap or tomorrow's planned session demands
  • the message is written in a sendable Coach Luca voice and matches current attribution rules
  • the recommendation clearly reflects the athlete's training context and health context
  • lower-priority nuance that would overload the athlete message is preserved in the internal review rather than forced into the athlete-facing message

Relationship to other skills

  • Use nutrition-intake first if the day still contains unprocessed nutrition items.
  • Use nutrition-intake for any required item-level nutrition entry repair before doing the daily review.
  • Use nutrition-reply as the canonical wording guardrail for the final athlete-facing nutrition message body.
  • When saving the daily-review outbound message, use the canonical daily-log outbound-message area under ## Messages, consistent with ### Morning plan and ### Evening summary, and place ### Nutrition review immediately after ### Evening summary when both are present.
  • If the daily review is being combined into a broader evening note, Coach Luca may synthesize it, but the nutrition agent's internal review should still be written first.
  • When the workflow is a morning-after review of yesterday, treat yesterday as the evidence target and today as the log target.