wellcaffeinated Notes — Reflect
A periodic review skill. Read the vault, synthesise, present. Do not create or modify anything unless the user explicitly asks.
Before starting
Invoke the notebook:notes-workflow skill before proceeding. It verifies the vault connection, reads VAULT.md for conventions, and provides the CLI patterns this skill depends on. If it is not available, ask the user to install the notebook plugin.
What this skill does
- In parallel: query recent daily note activity and project state — see VAULT.md for how to access each
- Read individual daily notes and relevant project notes in full for detail
- Identify themes, recurring topics, open questions, and wins
- Present a structured synthesis to the user
Handling ambiguity
Daily notes and project notes are often messy and lack context. If a note's meaning or intent is unclear, don't guess — flag it when presenting the synthesis and ask the user what they meant or what the outcome was. This is especially useful for single-line entries or cryptic shorthand.
Suggested structure for the reflection output
- What you worked on — projects and topics that appeared across the period
- Themes — patterns or ideas that recurred
- Open questions — things that came up but weren't resolved
- Wins — things that got done
- Possible next actions — surfaced from context, not prescriptive
Read-only by default
Present findings conversationally. If the user wants a reflection note created, ask where they'd like it filed before creating anything.