sync-project

To automatically sync project progress to a Notion dashboard, you need a tool that parses planning documents and aggregates Git logs into formatted markdown. This Skill automates that process by extracting phase progress and session notes, then writing them directly to client-facing and internal Notion pages via the API.

Yes, you can update both client-facing and internal Notion pages from a single source. The Skill parses your prompt_plan.md frontmatter and body, aggregates the Git version history, and writes formatted markdown sections to multiple specified Notion pages simultaneously.

To preview project status updates before writing to Notion, run the synchronization command with the --check-only flag. This allows you to review the extracted prompt_plan.md data and aggregated Git logs without pushing any changes to the Notion API.

No, this project synchronization tool requires a Git repository to function correctly. It specifically aggregates Git logs and reads accumulated session data to compile project status, meaning Git version history is a necessary dependency for generating accurate Notion dashboard updates.

The best way to automate sprint status reporting to Notion is using a tool that reads prompt_plan.md and Git logs to generate dashboards. This Skill extracts phase progress and session-captured notes, pushing formatted updates to Notion pages after each sprint without manual editing.

If your Notion pages are not updating during project sync, you may need to use the --force flag to override stale data checks. Alternatively, you can run with --skip-notion to verify that prompt_plan.md parsing and Git log aggregation are completing successfully before attempting the API write.