Read reference/integrations.md Calendar section for provider details.
Check calendar integration status; if not configured, return {"status": "not_configured"}.
Resolve {target_date} to YYYY-MM-DD format.
Execute the list_events operation with {target_date} and offset=1.
For each event extract: time, title, attendee names.

Return JSON:
{
  "status": "ok" | "not_configured" | "error",
  "events": [{"time": "...", "title": "...", "attendees": ["..."]}],
  "error": null | "description"
}

Read reference/integrations.md Tasks section for provider details.
Execute the list operation for the primary task list (default: Active).
Identify tasks due {target_date} or highest priority.
Execute the overdue operation to check for overdue tasks.

Return JSON:
{
  "status": "ok" | "not_configured" | "error",
  "tasks_due_today": [{"title": "...", "due": "...", "list": "..."}],
  "overdue": [{"title": "...", "due": "...", "list": "..."}],
  "top_priority": [{"title": "...", "due": "...", "list": "..."}],
  "error": null | "description"
}

Read memory/people/_index.md.
Look up profiles for these meeting attendees: {attendee_names_if_known}
Read memory/initiatives/_index.md and find relevant initiative context.
Read reference/schedule.md if it exists; identify [RECURRING] and [ONCE] items due {target_date}.
Read inbox/pending/ and count pending items.
Read reference/.housekeeping-state.yaml for last housekeeping run.
Read reference/maturity.yaml for maturity level.

Return JSON:
{
  "people_context": [{"name": "...", "summary": "...", "open_items": ["..."]}],
  "initiative_context": [{"name": "...", "status": "..."}],
  "scheduled_items": [{"type": "recurring|once", "description": "..."}],
  "inbox_count": 0,
  "housekeeping_last_run": "YYYY-MM-DD",
  "housekeeping_streak": 0,
  "plugin_version": "0.0.0",
  "last_reference_update": "YYYY-MM-DD",
  "last_index_rebuild": "YYYY-MM-DD",
  "maturity": {"level": 1, "people": 0, "meetings_processed": 0},
  "p1_alerts": []
}

P1 alert detection: populate `p1_alerts` array with string messages if any of these conditions are true:
- `housekeeping_last_run` is >3 days ago → "Housekeeping hasn't run in {N} days. Run `/maintain health`."
- `last_index_rebuild` is >30 days ago or null → "Index rebuild recommended. Run `/maintain rebuild`."
- `inbox_count` > 20 → "Inbox has {N} pending items. Run `/maintain inbox`."

### Today's schedule
- Chronological list with time, title, prep needed

### Scheduled items due today
- Recurring and one-time items from reference/schedule.md

### Priority tasks
- Top 3-5 tasks for today
- Flag tasks that should be done before specific meetings

### People I'm meeting
- Brief context for each person
- Open items or follow-ups with them
- Questions to ask or responses owed

### Focus opportunities
- Open time slots for deep work
- Suggested task for each slot

### System status
- TARS maturity: Level [N] ([X] people, [Y] meetings). Next: [milestone]
- Inbox: [N] items pending
- Last housekeeping: [date] (streak: [N] days)
- Plugin: v[X.Y.Z] (reference files updated: [date])

### Attention needed
(Only include this section if p1_alerts is non-empty. List each alert as a bullet point.)

Read reference/integrations.md Calendar section for provider details.
Check calendar integration status; if not configured, return {"status": "not_configured"}.
Resolve {monday_date} to YYYY-MM-DD format.
Execute the list_events operation with {monday_date} and offset=7.
Identify high-priority meetings (executives, leadership, key stakeholders).
Identify open time slots.

Return JSON:
{
  "status": "ok" | "not_configured" | "error",
  "events": [{"date": "...", "time": "...", "title": "...", "attendees": ["..."], "priority": "high|normal"}],
  "open_slots": [{"date": "...", "start": "...", "end": "...", "duration_minutes": 0}],
  "error": null | "description"
}

Read reference/integrations.md Tasks section for provider details.
Execute the list operation for all configured lists (default: Active, Delegated, Backlog).
Execute the overdue operation.
Identify tasks due this week ({monday_date} through {sunday_date}).
Identify tasks related to meeting topics if known.

Return JSON:
{
  "status": "ok" | "not_configured" | "error",
  "tasks_due_this_week": [{"title": "...", "due": "...", "list": "...", "owner": "..."}],
  "overdue": [{"title": "...", "due": "...", "list": "..."}],
  "backlog_stale": [{"title": "...", "created": "...", "days_old": 0}],
  "completed_last_week": [{"title": "...", "completed": "..."}],
  "error": null | "description"
}

Read memory/people/_index.md + profiles of frequent meeting attendees.
Read memory/initiatives/_index.md + active initiative details.
Identify responses owed and follow-ups needed.
Read journal/{last_week_month}/_index.md for last week entries.
Read reference/schedule.md if it exists; identify items due this week.
Read inbox/pending/ and count pending items.
Read reference/.housekeeping-state.yaml for last housekeeping and index rebuild dates.
Read reference/maturity.yaml for maturity level.

Return JSON:
{
  "people_context": [{"name": "...", "summary": "...", "responses_owed": ["..."], "follow_ups": ["..."]}],
  "initiatives": [{"name": "...", "status": "...", "milestones_this_week": ["..."]}],
  "last_week_entries": [{"date": "...", "type": "...", "title": "..."}],
  "scheduled_items": [{"type": "recurring|once", "description": "...", "due": "..."}],
  "inbox_count": 0,
  "housekeeping_last_run": "YYYY-MM-DD",
  "housekeeping_streak": 0,
  "plugin_version": "0.0.0",
  "last_reference_update": "YYYY-MM-DD",
  "last_index_rebuild": "YYYY-MM-DD",
  "maturity": {"level": 1, "people": 0, "meetings_processed": 0},
  "p1_alerts": []
}

P1 alert detection: populate `p1_alerts` array with string messages if any of these conditions are true:
- `housekeeping_last_run` is >3 days ago → "Housekeeping hasn't run in {N} days. Run `/maintain health`."
- `last_index_rebuild` is >30 days ago or null → "Index rebuild recommended. Run `/maintain rebuild`."
- `inbox_count` > 20 → "Inbox has {N} pending items. Run `/maintain inbox`."

### Last week summary
- Achievements (completed tasks, delivered items)
- Planned but incomplete (with reasons if known)

### This week's meetings
- **High-priority**: Leadership, clients, board meetings (flag)
- **All meetings**: Chronological with date/time, title, purpose

### Open tasks
- **Due this week**: Tasks with explicit due dates
- **Meeting-related**: Tasks connected to meeting topics
- **Preparation needed**: Items requiring work before meetings

### Milestones and initiatives
- Current week milestones
- Upcoming milestones needing advance preparation
- Initiative status updates

### People context
- **Responses owed**: Promises or follow-ups to people I'm meeting
- **Questions to ask**: Follow-up items or open threads

### Recommended focus time
- Open slots matched with highest priority tasks
- Specific time blocks with suggested assignments

### Backlog review
- Backlog items older than 90 days (flag as stale)
- Suggest: keep, reprioritize, or remove

### System status
- TARS maturity: Level [N] ([X] people, [Y] meetings). Next: [milestone]
- Inbox: [N] items pending
- Last housekeeping: [date] (streak: [N] days)
- Last index rebuild: [date]
- Plugin: v[X.Y.Z] (reference files updated: [date])

### Attention needed
(Only include this section if p1_alerts is non-empty. List each alert as a bullet point.)

1. Determine date/range and read integrations            [in_progress → completed]
2. Fetch calendar data (parallel sub-agent)              [pending → completed]
3. Fetch task data (parallel sub-agent)                  [pending → completed]
4. Query memory and context (parallel sub-agent)         [pending → completed]
5. Cross-reference and enrich data                       [pending → completed]
6. Generate and save briefing                            [pending → completed]

---
date: YYYY-MM-DD
title: Daily Briefing | Weekly Briefing
type: briefing-daily | briefing-weekly
---