Athlete daily log

Use this skill to maintain the canonical athlete daily log.

Keep doctrine lean and keep the day-file writing contract here. This skill is the entry point to the daily-log contract. The authoritative details live in the reference files linked below.

Scope

This skill governs:

• canonical daily-log structure
• section order and section intent
• section ownership in practice
• section writing patterns and templates
• storage rules for athlete-facing message bodies
• ## System event logging style
• repair and normalization passes for malformed daily logs

This skill does not decide the coaching content itself. Other skills still decide the coaching judgment for their domain, then write that judgment into the correct section using this contract.

Read these references when needed

• Read references/section-contract.md for the canonical section list, ownership, and what belongs in each section.
• Read references/section-templates.md for the standard writing patterns for Coach Luca, Endurance, Recovery, Strength, Nutrition, Messages, and System.
• Read references/system-events.md for ## System event style, event categories, and examples.
• Read references/repair-workflow.md when fixing malformed daily logs, migrating older logs, or consolidating duplicated content.
• Read references/examples.md when you need compact examples of well-formed sections.

Core rules

• Use the canonical daily-log path and section contract in references/section-contract.md.
• Use the section-writing patterns in references/section-templates.md.
• Use the ## System contract in references/system-events.md.
• Use the repair workflow in references/repair-workflow.md when normalizing malformed logs.
• Keep this skill body lean; do not duplicate detailed templates or section-specific formatting rules here when a reference file already owns them.
• Tilde escaping in tables: always write \~ (escaped tilde) inside Markdown table cells. Plain ~ triggers strikethrough in some renderers. This applies to the ## Nutrition summary table, the ## System table, and any other pipe table in the daily log. Exception: inside plain ~~~ fenced blocks, use plain ~ without escaping.

System table ordering rule (hard)

This rule applies every time a row is added to the ## System table. It is not optional and does not require reading the references first.

Before writing any new ## System row:

1. Read the current ## System table and identify the time of every existing row.
2. Determine the correct chronological position for the new row among existing rows.
3. Insert the new row at that position - do not append it to the end of the table if earlier rows already exist at a later time.
4. After writing, verify the table is still in ascending time order. If it is not, reorder before proceeding.

Hard failure mode to avoid: never append a new row to the end of the ## System table without first checking whether it is chronologically later than the current last row. If it is not, it must be inserted at the correct position. Out-of-order System rows are a log integrity failure.

Canonical file contract

Follow references/section-contract.md for the canonical path, section order, ownership, formatting rules, and message-storage rules.

If a file is missing sections, add only the sections needed for the current task unless a full repair pass is requested.

Writing pattern

When writing inside a daily log:

1. read the current file first
2. identify the owned section for the content
3. preserve unaffected sections
4. refresh or replace stale contradictory content instead of appending parallel versions
5. keep athlete-facing text verbatim when storing it under ## Messages
6. log workflow events under ## System
7. when writing ## System, rebuild the full table in chronological order rather than appending or anchor-inserting individual rows

Role boundary rule

Coach Luca may manage file structure, section order, and coordinator-owned sections. Coach Luca should not rewrite specialist analysis in another specialist's section unless the task is explicitly a migration, normalization, or repair pass. If a current-day specialist note is missing and the workflow requires a role status placeholder, add a clearly labeled coordinator-consolidated note inside that role's own section rather than moving the role update into ## Coach Luca.

Message and system rules

Follow references/section-contract.md for ## Messages storage. Follow references/system-events.md for all ## System requirements, including format, required fields, and examples.

Relationship to other skills

• morning-plan, evening-summary, athlete-checkin, and nutrition-daily-review should use this skill's log contract when writing to the canonical daily log.
• nutrition-intake remains the required path for item-level writes into ## Nutrition.
• This skill governs the daily-log container and section-writing rules, not the domain logic inside other skills.

Completion standard

The task is complete only when:

• the affected daily log follows the canonical section contract closely enough for the task
• new content is written into the correct owned section
• athlete-facing outbound text is preserved verbatim under ## Messages when relevant
• process and delivery events are recorded under ## System when relevant
• no contradictory duplicate version of the same content remains in the file