weekly-synth

name	weekly-synth
description	Weekly rollup and planning with critical commitment preflight.
priority	P0
triggers	["/week"]

Weekly Synth

Use this skill for weekly planning, boss-readiness, and commitment rollups.

Required Preflight

Before synthesizing, run the critical commitment preflight:

python3 system/scripts/critical_commitment_refresh.py plan --mode week --json
python3 system/scripts/critical_commitment_refresh.py rank --mode week --json

If the plan reports should_pause_for_user: true, stop and show the user:

• What integration failed.
• Why the skipped source puts commitments at risk.
• The recommended fix.
• Safe options: reconnect/configure, paste/export for this run, skip once, or disable from defaults.

Do not continue with degraded source coverage until the user explicitly chooses a path.

Source Policy

• Use manifest-backed named read-only source windows by default for Slack, Outlook, Calendar, Teams, transcripts, Quill, Granola, Obsidian, Atlassian, and agent memory.
• Enabled, healthy TWG may supplement the named Atlassian window with one bounded personal work rollup under .agent/rules/TWG_READ_ONLY.md. Rovo/native reads remain primary for exact Jira or Confluence evidence.
• Backward source windows default to the last 5 business days and may shorten only when the chat/source manifest or command-run manifest shows a successful prior run for the same source/window. Calendar includes the last 5 business days of changes plus forward lookahead for upcoming active-workstream gates.