Maintain project diaries with atomic sync to Notion and Obsidian

Unified Diary System runs a four-step, mostly automatic workflow to summarize a work session into both a project-local dev log and a synced global diary, isolating per-project context while keeping a cross-project overview. Step 1 confirms the current directory name via pwd, never guessed, then writes achievements - git commits, file changes, task progress - into a project-scoped diary/YYYY/MM/YYYY-MM-DD-ProjectName.md, appending rather than overwriting and never mixing in other projects' content; a sub-step then runs prepare_context.py to refresh an AGENT_CONTEXT.md snapshot of the project. Step 2 runs fetch_diaries.py against the just-written local diary's path to print both today's global progress and the current project's progress side by side. Step 3 fuses those two materials mentally and writes them into a global diary ({diary_system_path}/diary/YYYY/MM/YYYY-MM-DD.md), enforcing a "context firewall" that forbids filing today's progress under a different project's existing heading, giving the current project's latest progress priority, and cleaning up any temp files created in the process. Step 4 runs master_diary_sync.py --sync-only to push the global diary to Notion and Obsidian, then extracts "Improvements and Learnings" from it, flags genuinely new or evolved rules, and pauses for explicit user confirmation before writing them into a knowledge base and running qmd embed. The whole flow is meant to run as one continuous tool-calling sequence across steps 1-4 - the skill explicitly forbids stopping to chat or ask "should I continue?" between those steps, reserving the only mandatory pause for the Step 4 knowledge-base confirmation. It ships two Markdown templates: a per-project local diary with a progress summary, execution details, troubleshooting, and checkbox next steps, and a global diary with per-project sections, an improvements and learnings section, and global action items.

Use it to summarize progress, write a daily dev log, or run a daily review while keeping each project's diary isolated and synced to Notion and Obsidian. Its acceptance criteria require, in order: a clean local diary with no cross-project pollution, a successful fetch_diaries.py run against an absolute path, a correctly appended global diary rewrite, a successful Notion/Obsidian sync, and a presented, user-authorized set of extracted learnings - skipping the final human confirmation step is not acceptable even though the rest of the flow runs autonomously.

Input: the current session's git commits, file changes, and task progress, plus the confirmed project directory name. Output: an appended project-local diary file, a fused and appended global diary file, a refreshed AGENT_CONTEXT.md, a Notion and Obsidian-synced copy of the global diary, and, after user confirmation, an updated knowledge-base entry.

• scripts/prepare_context.py, scripts/fetch_diaries.py, and scripts/master_diary_sync.py for context refresh, material extraction, and cloud sync
• Notion and Obsidian, as the sync targets
• A local knowledge base plus qmd embed, for confirmed learnings

Anyone running a daily dev-log or progress-review workflow across multiple projects who wants isolated per-project diaries automatically fused into a synced global overview, with human sign-off only on genuinely new lessons learned.