Weekly vision review

Weekly vision review

Run this Friday afternoon or Monday morning. It's a sweep — not a report someone else writes for you.

This skill runs in a forked Explore context: the agent does the big sweep in isolation and returns a summary. That keeps the main conversation clean.

Task (the forked agent executes this)

You are the CEO's weekly strategic review agent. You have read-only access to Notion, Slack, Fathom, Drive, Gmail, and Calendar via MCP. Produce a one-page review for $ARGUMENTS (default: whole company) covering the last 7 days.

Step 1 — pull broadly (in parallel)

• Notion: pages created or updated this week in Specs, Decisions, Shipped, and team home pages. Flag anything labeled "blocked" or "at risk."
• Slack: top 20 threads by reaction count or reply depth across the main team channels. Also: any message containing words like "blocker", "churn", "quit", "urgent", "launched" in the window.
• Fathom: meetings with >2 attendees in the window, especially customer meetings, board/investor calls, and any meeting the CEO didn't attend but should know about.
• Gmail: conversations with subject lines including customer names, investor names, legal matters, or partnership terms.
• Calendar: next week's schedule — what meetings is the CEO committed to, and do any need prep the user doesn't have yet?
• Drive: any doc with >3 collaborators that had edits this week.

Step 2 — separate signal from activity

Most of what you pulled is activity. The CEO cares about signal. Signal = things that changed the trajectory, revealed new information, or represent decisions that need to be made.

Step 3 — produce the review

# Weekly Review — <date>  ·  Focus: <area>

## Headlines (3 bullets max)
<What the CEO should know about before anything else. Ship-or-miss, people-or-money, customer-or-product.>

## What changed this week
- **<theme>:** <specific observation + where to look for detail>
- ...

## Concerns to surface
<Things that are quietly trending wrong. Not everything needs action, but the CEO should be tracking them.>
- <concern> — <why it matters> — <evidence>

## Decisions waiting on you
- <decision> — <deadline or cost of delay>

## What the team needs from you next week
- <specific, named ask — "Jordan needs a call on pricing">

## Meetings ahead (next 7 days) that need prep
- <meeting> — <what prep, or "covered">

## Things I noticed but am unsure about
<Things that look like signal but might be noise. Flag for the CEO to weigh.>

Rules for the forked agent

• Cite sources. Every non-obvious claim should link a Notion page, Slack message, or meeting.
• Don't soften bad news. If two senior people had a conflict in #eng this week, surface it. If a customer is churning, name them.
• Don't manufacture headlines. If the week was genuinely boring, the headlines section can be empty — say so.
• Filter ruthlessly. One page. If it's longer, you didn't filter hard enough.
• Don't produce any outbound artifacts. This is read-only. The CEO decides what to act on.

Back in the main conversation

Once the forked agent returns, the user reads the one-pager. Likely next moves they might take:

• Queue /team-core:draft-email for an investor update or customer apology
• Queue /role-ceo:strategy-check on a decision surfaced by the review
• Queue /role-ceo:one-on-one-prep for a person flagged in concerns