Daily Note Wrap-Up Workflow

Use this skill for evening wrap-up work that creates tomorrow's daily note and updates the monthly daily-note index.

Core rules

• Treat the requested daily-note structure as a contract; preserve section order exactly.
• Carry forward incomplete work into tomorrow's note.
• On weekends, omit any work-specific section (for example ### [Work]) entirely rather than leaving an empty heading or placeholder bullet.
• If a section has nothing to place, follow the user's exact omission rule for that section rather than inventing filler text.
• Keep today's note untouched; only create or update tomorrow's note and the monthly index.
• Serialize all mutations to the same file. Never launch parallel patches against one note or monthly index; combine related edits into one cohesive patch when practical, or patch sequentially with a read-back between changes.

Structure gotchas

• The daily note template is not a generic form: match the user's requested headings and ordering exactly, including weekend-only omissions.
• Do not leave a blank ### [Work] heading on weekends; remove the section entirely.
• Use None only where the requested structure explicitly asks for it (for example, Waiting / Blocked), and omit empty sections otherwise.