daily-plan

Quick Start

What to provide: Nothing required. Just run it.

/daily-plan              → Compact daily plan (default: TL;DR + Top 3 + Schedule + Heads Up)
/daily-plan full         → Full daily plan with all sections (metrics, email, strategic alignment)
/daily-plan tomorrow     → Preview tomorrow's plan (evening planning)

What you get: A prioritized daily plan with meeting context, tasks, and flags. Pulls from your PRDs, meetings, stakeholder profiles, and connected MCPs automatically.

Time: 2-5 minutes. Faster with MCPs connected.

Same-Day Plan Detection

Before generating a new plan, check thoughts/shared/pm/reports/ for an existing plan from today.

If a same-day plan exists:

I see you already have a plan for today (`thoughts/shared/[filename]`).

Options:
1. **Update it** - I'll refresh with new context (meetings changed, priorities shifted)
2. **Replace it** - Start fresh (I'll archive the old one as `[filename]-v1.md`)
3. **Keep it** - No changes needed

Which would you prefer?

If no same-day plan exists: Proceed normally.

Purpose

Start your day with a comprehensive plan that pulls together everything you need: meetings with attendee context, active PRDs, open tasks, metrics to monitor, and stakeholder intelligence.

Inspired by personal operating system patterns but tailored specifically for Product Managers.

Usage

• /daily-plan - Create today's daily plan (compact mode by default)
• /daily-plan full - Full daily plan with all sections
• /daily-plan tomorrow - Preview tomorrow (evening planning)

Context Routing

Check these files first:

1. thoughts/shared/pm/frameworks/ - Quarter priorities, OKRs, North Star
2. thoughts/shared/pm/reports/ - This week's priorities (if /weekly-plan was run)
3. thoughts/shared/pm/prds/ - Active PRDs and their stages
4. thoughts/shared/pm/context/stakeholder-*.md - Stakeholder profiles and communication styles
5. thoughts/shared/product/meeting-notes/ - Recent meeting context
6. thoughts/shared/pm/launches/ - Recently launched features (past 2 weeks)

Integration Options (Multiple Paths):

Option 1: MCP Servers (Recommended - Automated)

• Google Calendar MCP - Auto-fetch today's meetings
• Gmail MCP - Scan recent important emails
• Linear MCP - Query open tasks
• PostHog/PostHog MCP - Pull metrics for features
• Slack MCP - Recent team communications

Option 2: Direct API Access (If MCPs Not Available)

• Google Calendar API - I can help you set up API access and fetch via curl or Python
• Gmail API - Fetch unread/important emails via API calls
• Linear API - Query tasks via GraphQL API
• PostHog REST API - Pull dashboard data
• Setup guide: I'll walk you through getting API keys and making first calls

Option 3: Export/Import Workflow (Manual but Works)

• Calendar: Export today's calendar as .ics → I'll parse it
• Email: Forward important emails → I'll extract context
• Tasks: Export Linear to CSV → I'll process it
• Metrics: Screenshot dashboard → I'll analyze with vision
• Setup guide: I'll show you how to export from each tool

Option 4: Browser Automation (Semi-Automated)

• Using Claude in Chrome MCP: I can navigate to your tools and extract data
• Google Calendar: Open in browser → scrape today's events
• Gmail: Open inbox → extract recent threads
• Linear: Open your view → pull assigned tasks
• Analytics: Open dashboard → read metrics
• Setup guide: I'll help configure Chrome automation

Option 5: Manual Input (Always Available)

• I ask targeted questions and you provide quick answers
• Takes 2-3 minutes but works without any setup
• Useful for first time or when tools are down

Fallback Strategy: If no integrations available, I'll:

1. Use file-based data (meeting notes, task lists in PM OS)
2. Ask focused questions (5-6 quick inputs from you)
3. Generate plan with placeholders you can fill in

Workflow

Step 1: Pre-Flight Checks

1. Determine target date:
2. Default: Today
3. If user said "tomorrow": Tomorrow's date
4. Calculate day of week, week number

1. Check for yesterday's plan (carry-over):
2. Read thoughts/shared/pm/reports/ for yesterday's plan file
3. If found: Identify which items were likely completed vs. deferred based on:
4. Items with checkboxes still unchecked
5. P0 tasks that had no time blocked
6. Items flagged in "Heads Up" as at-risk
7. Open with: "Carrying over from yesterday: [deferred items]."
8. If no previous plan exists, skip this step.

1. Check for weekly plan:
2. Read thoughts/shared/pm/reports/YYYY-WXX-weekly-plan.md for current week
3. If exists: Extract this week's Top 3 priorities
4. If missing: Note that week isn't planned (suggest /weekly-plan)

1. MCP availability check:
2. Attempt to query each MCP silently
3. Note which MCPs are connected
4. Plan graceful fallback for missing MCPs

Step 2: Context Gathering (Run in Parallel)

A. Calendar & Meetings (Calendar MCP or manual):

If Calendar MCP available:

Query: Get events for [target date]
Extract:
- Meeting times
- Meeting titles
- Attendee names/emails
- Meeting descriptions

For each meeting:

• Look up attendees in thoughts/shared/pm/context/stakeholder-*.md
• Scan thoughts/shared/product/meeting-notes/ for recent interactions with each person
• Note: What was discussed last time, open action items

Flag issues:

• Back-to-back meetings (no break between)
• Meetings without prep notes
• Meetings with stakeholders you haven't synced with recently

If Calendar MCP not available:

• Ask user: "What meetings do you have today?"
• Or read from manual calendar file if one exists

B. Email Context (Gmail MCP or manual):

If Gmail MCP available:

Query: Get unread/important emails from past 24 hours
Filter:
- Emails from stakeholders (match against stakeholder profiles)
- Emails with keywords: "urgent", "decision", "review", "feedback"
- Thread participants you're meeting with today

Extract:

• Open questions you need to answer
• Decisions waiting on you
• Context for today's meetings

If Gmail MCP not available:

• Skip this section or ask: "Any important emails I should know about?"

C. Active PRDs & Initiatives:

Scan thoughts/shared/pm/prds/:

• Check file modification dates (recently updated = active)
• Read frontmatter or first section to determine stage:
• Team Kickoff
• Planning Review
• XFN Kickoff
• Solution Review
• Launch Readiness
• Impact Review

For each active PRD:

• Note: What stage it's in
• What the next milestone is
• Who's blocking progress (if stalled)

Cross-reference with thoughts/shared/pm/frameworks/:

• How does each PRD map to quarter priorities?
• Which strategic pillar does it support?

D. Tasks & Action Items (Linear MCP or files):

If Linear MCP available:

Query: Get tasks assigned to user, status != Done
Filter by priority/labels:
- P0 or "urgent" or "blocker"
- P1 or "important"
- P2 or default

If MCP not available:

• Scan thoughts/shared/product/meeting-notes/ for unchecked action items
• Look for task lists in recent notes

Categorize:

• P0 (Must do today): Blockers, urgent, time-sensitive
• P1 (Important this week): High-impact, supports weekly priorities
• P2 (If time allows): Nice-to-have, low urgency

E. Metrics to Monitor (Analytics MCP or files):

Check thoughts/shared/pm/launches/ for features launched in past 2 weeks.

For each recent launch: If Analytics MCP available:

Query: Get key metrics for [feature]
Time range: Since launch date
Metrics: Adoption, engagement, conversion (based on PRD success criteria)

If MCP not available:

• Check if metrics file exists in thoughts/shared/pm/metrics/
• Or note: "Manual check needed for [feature] metrics"

Flag:

• Metrics tre