weekly-report

name	weekly-report
description	Generate summary of 1:1 and meeting notes organized by audience, wins, and kudos
argument-hint	["weeks"]
auto-approve	true

Weekly Report Agent

Generate an executive summary of notes from your 1:1 docs, meeting docs, and Slack conversations for the past week(s), organized by staff-meeting audience, local team emphasis, broad communication, wins, and kudos. With references. Aim for 20+ total docs or channels.

Overview

This agent helps you:

1. Review recent notes from all your 1:1 and recurring meeting docs, and Slack
2. Identify key topics that need communication
3. Categorize items by audience (leadership staff meeting, local team, everyone), wins, and kudos

Prerequisites

• @AGENTS.override.md file with your 1:1 docs, meeting docs, and Slack channels
• Configured Dropbox MCP access for Paper and Atlassian Rovo MCP for Confluence/JIRA context

Usage Pattern

Step 1: List Your Documents

Get all 1:1 docs, meeting docs, and Slack channels and Slack DMs from @AGENTS.override.md These may be Confluence pages or Dropbox Paper docs

Step 2: Process Documents in Batches

IMPORTANT: Use batch processing to handle large numbers of documents efficiently.

Process all documents in batches of 12-15 documents at a time. For each batch:

1. Fetch documents for this batch (continue on errors - see Error Handling below)
2. Immediately extract notes from recent time period (last 7 days by default)
3. Categorize extracted notes into the 5 categories (see Category Definitions below)
4. Append categorized notes to $TMP_DIR/notes_batch_N.md (where N is batch number). Create $TMP_DIR with mktemp -d "${TMPDIR:-/tmp}/weekly-report.XXXXXX" and clean it up with a trap.
5. Discard full document content from context (only keep extracted notes file)

Document batching strategy:

• Batch 1 (12-15 docs): 1:1 docs (prioritize recent/active relationships)
• Batch 2 (12-15 docs): Meeting docs + remaining 1:1s
• Batch 3 (12-15 docs): High-priority Slack channels (P0)
• Batch 4+ (12-15 docs each): Remaining Slack channels and DMs

After completing ALL batches, proceed to Step 3 (consolidation).

For Slack channels, use the /slack skill to read messages from the last 10 days:

1. Calculate date 10 days ago: date -v-10d '+%Y-%m-%d'
2. Use slack_search_messages with after:YYYY-MM-DD in:#channel-name query and pagination
3. Format results as Markdown (see /slack skill for formatting example)

For Confluence and Paper docs, use Atlassian Rovo MCP for Confluence and Dropbox MCP (dropbox-mcp) paper_read_document for Paper. For Paper docs, fall back to the Chrome plugin/live Paper view second when Dropbox MCP is unavailable or lacks the needed operation. Use /confluence, /dropbox, or sidekick.clients.dropbox only as final fallbacks when the preferred MCP and Chrome paths are unavailable or unsuitable, DROPBOX_ACCESS_TOKEN is set, debugging the local client, running standalone workflows, or the user explicitly asks for the local client.

Look for notes from recent time period:

• Date headers (e.g., "January 31, 2026", "Week of 1/27")
• Bullet points under recent dates
• Action items or discussion topics
• Important: Ignore content under date headers older than your target time period

Error Handling Strategy

When a document fails to fetch:

1. Log the error with document name and error type (but DO NOT stop processing)
2. Continue to the next document - process all documents in the batch regardless of failures
3. Track failures in a list with categories:
   • Auth failures (403/401): Document URL + error message
   • Not found (404): Document URL
   • Rate limits (429): Document URL (client will auto-retry once)
   • Other errors: Document URL + error type
4. Report all failures at Step 5 (Document Summary) by category

Error response format (to be included in Step 5 output):

⚠️ Failed to fetch X documents:

Auth failures (403/401):
- [Doc name](URL) - 403 Forbidden

Not found (404):
- [Doc name](URL) - Document not found

Rate limits (429):
- [Doc name](URL) - Rate limit hit (retried)

Other errors:
- [Doc name](URL) - Error message

IMPORTANT: Never stop processing due to a single document failure. The goal is to extract as much context as possible from available documents.

Step 3: Consolidate Notes from All Batches

After processing all batches:

1. Read all batch notes files ($TMP_DIR/notes_batch_*.md)
2. Merge notes by category (combine all "Leadership Staff Meeting" items, all "Local Team" items, all "Wins" items, etc.)
3. Deduplicate similar notes across batches:
   • If same topic appears in multiple docs, consolidate into ONE note
   • Keep ALL [ref] links from all sources
   • Example: Topic X happened [ref1](url1) [ref2](url2)
4. Prioritize within each category by importance/urgency
5. Write consolidated report to memory/weekly_report.md

Step 4: Category Definitions

Sort extracted notes into the following categories. Each category should be a bullet list of notes. Each note should include a [ref] link to the source document URL from @AGENTS.override.md.

Format examples:

- Single source: Your note text here [ref](https://document-url-from-claude-local-md)
- Multiple sources: Topic X happened [ref1](url1) [ref2](url2)

Writing Style and Link Hygiene

The final report should be easy to copy/paste into meeting notes or Slack without sounding generated.

• Write in Chase's normal operating voice: direct, plain, concise, and specific.
• Use first person when Chase owns the action or ask: "I'm proposing...", "I need approval...", "I'm creating...", "We're actively working on...".
• State the practical implication, not just the synthesized theme. Prefer "MTI is in danger of not making the Q3 cut line because Sharing capacity is the blocker" over abstract phrasing like "MTI and Sharing have become the main Q3 cut-line decision."
• Call roadmap slips, staffing asks, explicit approvals needed, and decision points directly.
• Keep bullets short enough to paste into staff-meeting notes: usually 1-2 sentences, with links at the end.
• Avoid consultant or artifact-heavy language when a simpler phrase works. Examples to avoid: "has become the main decision," "leadership-level call," "live leadership issue," "one-time calibration artifact," "shifting into a management system."
• Prefer shareable links in the copy/paste sections: unrestricted or broadly accessible Paper docs, Confluence docs, Google Drive docs/sheets, Jira issues, and Slack channels when the target audience can access them.
• Avoid personal DMs, private 1:1 docs, and local miclog/memory file links in the copy/paste sections unless no shareable source exists. Use those private/local sources for synthesis, but link to a broader shareable source that supports the point when possible.
• Never invent a URL. If no shareable link is available, omit the link or include the best broader shareable source and keep private/local details out of the paste-ready text.

Things to Report to Your Leadership Staff Meeting

Items that require escalation, alignment, approval, or visibility in the user's manager's-manager staff meeting:

• Roadmap changes or delays
• Cross-team dependencies or blockers
• Resource needs (headcount, budget)
• Strategic decisions needed
• Risk escalations
• Organizational topics
• Business wins
• Recognition and wins to share

Things to Emphasize to Your Team

Items relevant to the user's local team, managers, and direct reports:

• Feedback from leadership
• Changes to team priorities or roadmap
• Process updates
• Career development opportunities
• Team resource changes
• Kudos from leadership

Things to Communicate to Everyone

Items for broad communication:

• Product launches or milestones
• Company announcements
• Cross-org initiatives
• Demos or show-and-tells
• Policy or process changes
• Team wins worth celebrating

Wins

Concrete positive outcomes from the reporting period. Prefer outcomes that are already shipped, launched, completed, unblocked, improved, or measurably trending better:

• Product launches, rollouts, ramps, and GA milestones
• Revenue, growth, adoption, reliability, performance, or cost-savings impact
• Operational improvements or process wins
• Technical debt reductions, platform migrations, or tooling improvements
• Planning, dependency, or alignment breakthroughs

Kudos

Thank yous for specific people:

• Person went above and beyond
• Any impact attributable to a person

Step 5: Final Output

1. Print document processing summary:

   • Total documents attempted
   • Successfully processed by type (1:1s, meetings, Slack)
   • Failed documents with error details (see Error Handling format above)

2. Write consolidated report to memory/weekly_report.md with:

   • All categorized notes from Step 3
   • Each note with [ref] links to source documents
   • Deduplicated entries with multiple references where applicable

3. Echo the report contents to chat AND provide relative path to the memory file

Report structure:

# Weekly Report - [Date Range]

## Things to Report to Your Leadership Staff Meeting
- Item 1 [[ref]](url)
- Item 2 [[ref1]](url1) [[ref2]](url2)

## Things to Emphasize to Your Team
- Item 1 [[ref]](url)

## Things to Communicate to Everyone
- Item 1 [[ref]](url)

## Wins
- Win 1 [[ref]](url)

## Kudos
- Person X for Y [[ref]](url)

This report generated using [chase-sidekick](https://github.com/chase-seibert/chase-sidekick) and the [weekly-report skill](https://github.com/chase-seibert/chase-sidekick/tree/main/.agents/skills/weekly-report).

Tips

• Time Period: Default to last 7 days, adjust based on your reporting cadence
• Batch Size: Keep batches to 12-15 documents to avoid context window issues
• Date Parsing: Look for date headers in various formats:
  • "January 31, 2026"
  • "2026-01-31"
  • "Week of 1/27"
  • "1/31"
• Bullet Points: Most notes are in bullet format under date headers
• References: Each note should end with [ref](URL) linking to the source doc URL from @AGENTS.override.md
• Deduplication: Same topic might appear in multiple docs - consolidate but keep all references
• Prioritization: Within each category, order by importance/urgency
• Context Management: Discard full document content after extracting notes from each batch to preserve context window
• Batch Files: notes_batch_*.md files are intermediate artifacts in $TMP_DIR; the final consolidated report goes in weekly_report.md