dcurlewis/.claude/skills/morning

Morning

Generate today's daily journal entry using the stable baseline flow below.

/setup may personalise the optional module section at the end of this file. Always run the baseline. Only run optional module instructions when they are explicitly present in the generated section.

Module Model

This skill has two parts:

1. Baseline flow: Generic behaviour that should work for all users
2. Generated modules: Optional additions maintained by /setup

Generated modules plug into the baseline through named hooks:

• PRECHECKS: Run before calendar work begins
• ENRICHMENT: Run after the core agenda draft is built
• WEEKLY_TASKS: Run after the baseline weekly tasks list is created
• TASK_BOARD: Run after weekly tasks are finalised
• SUMMARY: Apply when composing the final chat response

If a hook has no configured modules, skip it silently.

Pre-Requisites

• Guidelines/daily-journal-template.md is the structural reference
• Calendar data is helpful but not mandatory
• Optional modules may declare additional prerequisites; honour them when present

Process

Step 0: Load generated morning modules

1. Read the section between <!-- GENERATED: morning-modules:start --> and <!-- GENERATED: morning-modules:end -->
2. Note any configured modules under each hook
3. Track any optional output they request, such as:
   • extra post-agenda sections
   • extra post-weekly sections
   • ### Automation Status
   • extra summary lines for chat
4. If the generated section says no modules are configured, continue with the baseline only

Never rewrite the generated section while running /morning. /setup owns that part of the file.

Step 1: Run PRECHECKS modules

Execute configured PRECHECKS modules in the order they appear.

• If a module is informational, collect its output for later sections
• If a module declares a blocking prerequisite and it is unmet, stop and tell the user what needs to happen before /morning can continue
• If a module produces automation-status lines, save them for the optional ### Automation Status section

Step 2: Fetch calendar data

Check whether Synced-Data/Calendar/today.json already exists and is fresh for today.

• If it is fresh, reuse it
• If it is missing or stale, run the default connector (python3 Scripts/connectors/calendar-today.py) unless the user's environment clearly uses an alternative documented source
• If calendar generation fails or no connector is configured, inform the user and continue with a manual agenda placeholder

Step 3: Determine today's context

Use Synced-Data/Calendar/today.json when available to gather:

• today's date (YYYY-MM-DD)
• today's day name
• meetings, including times, titles, and attendees

If the calendar file is unavailable, fall back to the system date and create a journal with an empty agenda placeholder.

Step 4: Check idempotency

Check whether Curated-Context/Daily-Journals/YYYY-MM-DD.md already exists.

• If the file exists and already has a ### Agenda section, do not regenerate it. Tell the user: Journal already exists with agenda; nothing to do.
• If the file exists but does not yet have a ### Agenda section, preserve all existing human-written content and merge the AI-populated sections into the template structure
• If the file does not exist, create it fresh

Step 5: Resolve attendees to known people

Always resolve people systematically before enrichment. Never fabricate names.

For each meeting attendee:

1. Search Curated-Context/Entities/People/ by email address when available
2. If no email match exists, search by attendee name against:
   • Curated-Context/Entities/People/
   • Memory/memory-people.md
3. Use role, team, and recent-context clues to confirm likely matches
4. If an attendee still cannot be resolved:
   • do not fabricate a full name
   • do not create a wikilink for them
   • ask the user for clarification only if the missing identity blocks useful enrichment

Step 6: Build the core agenda

For each meeting in today's calendar:

1. Read the resolved person's entity stub when relevant
2. Look for the most recent related meeting insight in Curated-Context/Meeting-Insights/
3. Pull 1-3 concise context bullets at most, prioritising:
   • outstanding follow-ups from recent meetings
   • recent timeline entries from the person's stub
   • upcoming deadlines or changes relevant to that meeting
4. For recurring group meetings, look for the most recent prior instance and carry over unresolved agenda items when relevant
5. If there is no useful context, list only the meeting time and title

Formatting rules for the agenda:

• Use [[Person Name]] when you have a confirmed match
• Use [[YYYYMMDD-Meeting-Title]] when referencing previous meeting files
• Times should be HH:MM
• Keep enrichment concise; use bullets, not paragraphs

Step 7: Run ENRICHMENT modules

Execute configured ENRICHMENT modules after the core agenda is drafted.

Modules may:

• append additional agenda context
• add optional sections after ### Agenda
• add or update lines for ### Automation Status

Avoid duplication. If module content fits a specific meeting, prefer that meeting's agenda bullets over a separate section.

Step 8: Build memory-sourced notes

Create ### Notes using only information that does not belong under a specific meeting or optional post-agenda section.

1. Read the previous day's journal if one exists
2. Use its ### Notes section as the baseline for de-duplication
3. If present, also use ## End-of-Day Reflection:
   • ### Unresolved / Carry-over items may become candidates for today's notes
   • ### Tomorrow items that match today's meetings should move into agenda bullets instead
4. Scan the memory files for date-specific context:
   • Memory/memory-work.md
   • Memory/memory-context.md
   • Memory/memory-people.md
5. Include only items that are:
   • new today
   • specifically actionable today
   • materially changed since yesterday
   • the start or end of a relevant period

Do not repeat items already covered in:

• ### Agenda
• any optional post-agenda sections
• ### Weekly Tasks

Step 9: Build the baseline weekly tasks list

Create the initial ### Weekly Tasks content.

• Start with genuinely useful reminders that are specific to today
• If there are no baseline tasks, use a single placeholder line: -

Then execute configured WEEKLY_TASKS modules to append recurring routines, day-specific tasks, or generated links.

Step 10: Run TASK_BOARD modules

Execute configured TASK_BOARD modules after weekly tasks are finalised.

These modules may:

• surface active tasks into the journal
• add new task cards to a board when clearly appropriate
• add optional sections after ### Weekly Tasks

Only task-board modules may modify kanban-style board files. The baseline flow should not assume a board exists.

Step 11: Write the journal file

Write to Curated-Context/Daily-Journals/YYYY-MM-DD.md using Guidelines/daily-journal-template.md as the structural reference.

Replace the template placeholders:

• {{DATE}} → YYYY-MM-DD
• {{DAY_NAME}} → full day name
• {{NOTES_CONTENT}} → notes from Step 8
• {{AGENDA_CONTENT}} → agenda from Steps 6-7
• {{WEEKLY_TASKS_CONTENT}} → weekly tasks from Steps 9-10

Insert optional sections only when they have content:

• sections produced by ENRICHMENT modules go after ### Agenda
• sections produced by TASK_BOARD modules go after ### Weekly Tasks
• ### Automation Status goes after ### Weekly Tasks if any module produced status lines

Preserve any pre-existing human content when merging into an existing journal file.

Step 12: Compose the final chat summary

Keep the final summary to 4-6 lines maximum.

Default summary structure:

Morning briefing for [Day], [Date]:
- [N] meetings on today's agenda
- [N] weekly tasks captured (or "No weekly tasks")
- Journal: Curated-Context/Daily-Journals/YYYY-MM-DD.md

Apply any configured SUMMARY modules at this stage. They may add short, useful summary lines but should not turn the response into a verbose report.

Generated Morning Modules

This section is maintained by /setup. Re-running /setup may replace everything between the markers.

<!-- GENERATED: morning-modules:start -->

No optional morning modules are configured yet. Run /setup to personalise /morning.

<!-- GENERATED: morning-modules:end -->