name	daily-synth
description	Daily briefing and planning with critical commitment preflight.
priority	P0
triggers	["/day","/status","/morning","/brief","/now"]

Daily Synth

Use this skill for daily task aggregation and executive focus.

Required Preflight

Before synthesizing, run the critical commitment preflight:

python3 system/scripts/critical_commitment_refresh.py plan --mode day --json
python3 system/scripts/critical_commitment_refresh.py rank --mode day --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.
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.
Treat third-party systems as read-only. Never send, draft, reply, react, schedule, create, assign, transition, comment, upload, patch, delete, or move third-party state unless the user explicitly confirms that exact mutation in the current turn.
Use parallel agents for independent source reads and synthesis passes when the runtime supports them.
Keep shared writes serialized: Markdown task updates, source manifests, generated indexes, and final consolidation.
Stay within the 90-second wall-clock budget where possible. Prefer visible partial source gaps over silent skips.

Synthesis Rules

Direct manager, skip-level, and executive callouts outrank ordinary stale work.
External partner/customer/end-user commitments with agreed dates outrank internal undated work.
Completed outcomes stay visible with completion date/source.
Implied completions become confirmation questions.
Group output by workstream title first, never by Task Master ID.
User-facing task and workstream descriptions must use display_title plus source provenance, not hard IDs. Keep internal and source IDs only in local links, metadata, or an Agent refs line.
Evidence lines use this shape: [Task/workstream title]; started from [initial source label] on [date]; latest progress from [latest source label] on [date].

Output Shape

### Workstream Title
- Latest outcome: [succinct result, decision, or state]
  - Evidence: [task/workstream title; started from initial source on date; latest progress from latest source on date]
- Completed: [done item or "None newly confirmed"]
  - Completed: [date/source]
- Open items: [count or short list]
  - [Owner] - [action] by [date/gate], from [source]
- Recommended next 3:
  - [Action 1]
  - [Action 2]
  - [Action 3]

Más de este repositorio

mismo repositorio

ab-test-analysis

officebeats/beats-pm-kit

Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.

2026-07-188

agentic-memory

officebeats/beats-pm-kit

Local-first dual-pillar agentic memory inspired by TencentDB-Agent-Memory.

2026-07-188

ai-shaped-readiness-advisor

officebeats/beats-pm-kit

Assess whether your product work is AI-first or AI-shaped. Use when evaluating AI maturity and choosing the next team capability to build.

2026-07-188

autopilot

officebeats/beats-pm-kit

Full autonomous execution from idea to working code

2026-07-188

boss-tracker

officebeats/beats-pm-kit

Track high-priority leadership requests.

2026-07-188

company-profiler

officebeats/beats-pm-kit

Conducts deep-dive research to create a strategic dossier on a target company.

2026-07-188

Daily Synth

Use this skill for daily task aggregation and executive focus.

Required Preflight

Before synthesizing, run the critical commitment preflight:

python3 system/scripts/critical_commitment_refresh.py plan --mode day --json python3 system/scripts/critical_commitment_refresh.py rank --mode day --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.

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.

Treat third-party systems as read-only. Never send, draft, reply, react, schedule, create, assign, transition, comment, upload, patch, delete, or move third-party state unless the user explicitly confirms that exact mutation in the current turn.

Use parallel agents for independent source reads and synthesis passes when the runtime supports them.

Keep shared writes serialized: Markdown task updates, source manifests, generated indexes, and final consolidation.

Stay within the 90-second wall-clock budget where possible. Prefer visible partial source gaps over silent skips.

Synthesis Rules

Direct manager, skip-level, and executive callouts outrank ordinary stale work.

External partner/customer/end-user commitments with agreed dates outrank internal undated work.

Completed outcomes stay visible with completion date/source.

Implied completions become confirmation questions.

Group output by workstream title first, never by Task Master ID.

User-facing task and workstream descriptions must use display_title plus source provenance, not hard IDs. Keep internal and source IDs only in local links, metadata, or an Agent refs line.

Evidence lines use this shape:

[Task/workstream title]; started from [initial source label] on [date]; latest progress from [latest source label] on [date].

Output Shape

### Workstream Title - Latest outcome: [succinct result, decision, or state] - Evidence: [task/workstream title; started from initial source on date; latest progress from latest source on date] - Completed: [done item or "None newly confirmed"] - Completed: [date/source] - Open items: [count or short list] - [Owner] - [action] by [date/gate], from [source] - Recommended next 3: - [Action 1] - [Action 2] - [Action 3]