directory changes and restructuring

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

official-skills/notion-meeting-intelligence/SKILL.md

@@ -0,0 +1,295 @@
+---
+name: notion-meeting-intelligence
+description: Prepares meeting materials by gathering context from Notion, enriching with Claude research, and creating both an internal pre-read and external agenda saved to Notion. Helps you arrive prepared with comprehensive background and structured meeting docs.
+---
+
+# Meeting Intelligence
+
+Prepares you for meetings by gathering context from Notion, enriching it with Claude research, and creating comprehensive meeting materials. Generates both an internal pre-read for attendees and an external-facing agenda for the meeting itself.
+
+## Quick Start
+
+When asked to prep for a meeting:
+
+1. **Gather Notion context**: Use `Notion:notion-search` to find related pages
+2. **Fetch details**: Use `Notion:notion-fetch` to read relevant content
+3. **Enrich with research**: Use Claude's knowledge to add context, industry insights, or best practices
+4. **Create internal pre-read**: Use `Notion:notion-create-pages` for background context document (for attendees)
+5. **Create external agenda**: Use `Notion:notion-create-pages` for meeting agenda (shared with all participants)
+6. **Link resources**: Connect both docs to related projects and each other
+
+## Meeting Prep Workflow
+
+### Step 1: Understand meeting context
+
+```
+Collect meeting details:
+- Meeting topic/title
+- Attendees (internal team + external participants)
+- Meeting purpose (decision, brainstorm, status update, customer demo, etc.)
+- Meeting type (internal only vs. external participants)
+- Related project/initiative
+- Specific topics to cover
+```
+
+### Step 2: Search for Notion context
+
+```
+Use Notion:notion-search to find:
+- Project pages related to meeting topic
+- Previous meeting notes
+- Specifications or design docs
+- Related tasks or issues
+- Recent updates or reports
+- Customer/partner information (if applicable)
+
+Search strategies:
+- Topic-based: "mobile app redesign"
+- Project-scoped: search within project teamspace
+- Attendee-created: filter by created_by_user_ids
+- Recent updates: use created_date_range filters
+```
+
+### Step 3: Fetch and analyze Notion content
+
+```
+For each relevant page:
+1. Fetch with Notion:notion-fetch
+2. Extract key information:
+   - Project status and timeline
+   - Recent decisions and updates
+   - Open questions or blockers
+   - Relevant metrics or data
+   - Action items from previous meetings
+3. Note gaps in information
+```
+
+### Step 4: Enrich with Claude research
+
+```
+Beyond Notion context, add value through:
+
+For technical meetings:
+- Explain complex concepts for broader audience
+- Summarize industry best practices
+- Provide competitive context
+- Suggest discussion frameworks
+
+For customer meetings:
+- Research company background (if public info)
+- Industry trends relevant to discussion
+- Common pain points in their sector
+- Best practices for similar customers
+
+For decision meetings:
+- Decision-making frameworks
+- Risk analysis patterns
+- Trade-off considerations
+- Implementation best practices
+
+Note: Use general knowledge only - don't fabricate specific facts
+```
+
+### Step 5: Create internal pre-read
+
+```
+Use Notion:notion-create-pages for internal doc:
+
+Title: "[Meeting Topic] - Pre-Read (Internal)"
+
+Content structure:
+- **Meeting Overview**: Date, time, attendees, purpose
+- **Background Context**: 
+  - What this meeting is about (2-3 sentences)
+  - Why it matters (business context)
+  - Links to related Notion pages
+- **Current Status**: 
+  - Where we are now (from Notion content)
+  - Recent updates and progress
+  - Key metrics or data
+- **Context & Insights** (from Claude research):
+  - Industry context or best practices
+  - Relevant considerations
+  - Potential approaches to discuss
+- **Key Discussion Points**:
+  - Topics that need airtime
+  - Open questions to resolve
+  - Decisions required
+- **What We Need from This Meeting**:
+  - Expected outcomes
+  - Decisions to make
+  - Next steps to define
+
+Audience: Internal attendees only
+Purpose: Give team full context and alignment before meeting
+```
+
+### Step 6: Create external agenda
+
+```
+Use Notion:notion-create-pages for meeting doc:
+
+Title: "[Meeting Topic] - Agenda"
+
+Content structure:
+- **Meeting Details**: Date, time, attendees
+- **Objective**: Clear meeting goal (1-2 sentences)
+- **Agenda Items** (with time allocations):
+  1. Topic 1 (10 min)
+  2. Topic 2 (20 min)
+  3. Topic 3 (15 min)
+- **Discussion Topics**: 
+  - Key items to cover
+  - Questions to answer
+- **Decisions Needed**: 
+  - Clear decision points
+- **Action Items**: 
+  - (To be filled during meeting)
+- **Related Resources**:
+  - Links to relevant pages
+  - Link to pre-read document
+
+Audience: All participants (internal + external)
+Purpose: Structure the meeting, keep it on track
+Tone: Professional, focused, clear
+```
+
+See [reference/template-selection-guide.md](reference/template-selection-guide.md) for full templates.
+
+### Step 7: Link documents
+
+```
+1. Link pre-read to agenda:
+   - Add mention in agenda: "See <mention-page>Pre-Read</mention-page> for background"
+
+2. Link both to project:
+   - Update project page with meeting links
+   - Add to "Meetings" section
+
+3. Cross-reference:
+   - Agenda mentions pre-read for internal attendees
+   - Pre-read mentions agenda for meeting structure
+```
+
+## Document Types
+
+### Internal Pre-Read (for team)
+
+More comprehensive, internal context:
+- Full background and history
+- Internal metrics and data
+- Honest assessment of challenges
+- Strategic considerations
+- What we need to achieve
+- Internal discussion points
+
+**When to create**: Always for important meetings with internal team
+
+### External Agenda (for all participants)
+
+Clean, professional, focused:
+- Clear objectives
+- Structured agenda with times
+- Discussion topics
+- Decision items
+- Professional tone
+
+**When to create**: Every meeting
+
+### Agenda Types by Meeting Purpose
+
+**Decision Meeting**: Meeting Details → Objective → Options (Pros/Cons) → Recommendation → Discussion → Decision → Action Items
+
+**Status Update**: Meeting Details → Project Status → Progress → Upcoming Work → Blockers → Discussion → Action Items
+
+**Customer/External**: Meeting Details → Objective → Agenda Items (timed) → Discussion Topics → Next Steps
+
+**Brainstorming**: Meeting Details → Objective → Constraints → Ideas → Discussion → Next Steps
+
+See [reference/template-selection-guide.md](reference/template-selection-guide.md) for complete templates.
+
+## Research Enrichment Patterns
+
+Beyond Notion content, add value through Claude's capabilities:
+
+**Technical Context**: Explain technologies, architectures, or approaches. Provide industry standard practices. Compare common solutions. Suggest evaluation criteria.
+
+**Business Context**: Industry trends affecting topic. Competitive landscape insights. Common challenges in space. ROI considerations.
+
+**Decision Support**: Decision-making frameworks (e.g., RICE, cost-benefit). Risk assessment patterns. Trade-off analysis approaches. Success criteria suggestions.
+
+**Customer Context** (for external meetings): Industry-specific challenges. Common pain points. Best practices from similar companies. Value proposition framing.
+
+**Process Guidance**: Meeting facilitation techniques. Discussion frameworks. Retrospective patterns. Brainstorming structures.
+
+Note: Use general knowledge and analytical capabilities. Don't fabricate specific facts. Clearly distinguish Notion facts from Claude insights.
+
+## Meeting Context Sources
+
+**Project Pages**: Status, goals, team, timelines (most important)
+**Previous Meeting Notes**: Historical discussions, action items, decisions (recurring meetings)
+**Task/Issue Database**: Current status, blockers, completed/upcoming work (project meetings)
+**Specifications/Designs**: Requirements, decisions, approach, open questions (technical meetings)
+**Reports/Dashboards**: Metrics, KPIs, performance data, trends (executive meetings)
+
+## Linking Meetings to Projects
+
+**Forward Link**: Add meeting to project page's "Meetings" section
+**Backward Link**: Include "Related Project" section in agenda with project mention
+**Maintain bidirectional** links for easy navigation
+
+## Meeting Series Management
+
+**Recurring Meetings**: Create series parent page with schedule, meeting notes list, standing agenda, and action items tracker. Link individual meetings to parent.
+
+**Meeting Database**: For organizations, use database with properties: Meeting Title, Date, Type (Decision/Status/Brainstorm), Project, Attendees, Status (Scheduled/Completed)
+
+## Post-Meeting Actions
+
+Update agenda with:
+
+**Decisions**: List each decision with rationale and owner
+**Action Items**: Checkbox list with owner and due date (consider creating tasks in database)
+**Key Outcomes**: Bullet list of main outcomes
+
+## Meeting Prep Timing
+
+**Day-Before** (next-day meetings): Gather context → create agenda → share with attendees → allow review time
+**Hour-Before** (last-minute): Quick context → brief pre-read → basic agenda → essentials only
+**Week-Before** (major meetings): Comprehensive research → detailed pre-read → structured agenda → pre-meeting reviews
+
+## Best Practices
+
+1. **Create both documents**: Internal pre-read + external agenda for important meetings
+2. **Distinguish sources**: Label what's from Notion vs. Claude research
+3. **Start with search**: Cast wide net in Notion, then narrow
+4. **Keep pre-read concise**: 2-3 pages maximum, even with research
+5. **Professional external docs**: Agenda should be polished and focused
+6. **Enrich thoughtfully**: Claude research should add real value, not fluff
+7. **Link documents**: Pre-read mentions agenda, agenda mentions pre-read
+8. **Include metrics**: Data from Notion helps ground discussions
+9. **Share appropriately**: Pre-read to internal team, agenda to all participants
+10. **Share early**: Give attendees time to review (24hr+ for important meetings)
+11. **Update post-meeting**: Capture decisions and actions in agenda
+
+## Advanced Features
+
+**Meeting templates**: See [reference/template-selection-guide.md](reference/template-selection-guide.md) for comprehensive template library
+
+## Common Issues
+
+**"Too much context"**: Split into pre-read (internal, comprehensive) and agenda (external, focused)
+**"Can't find relevant pages"**: Broaden search, try different terms, ask user for page URLs
+**"Meeting purpose unclear"**: Ask user to clarify before proceeding
+**"No recent updates"**: Note that in pre-read, focus on historical context and strategic considerations
+**"External meeting - no internal context"**: Create simpler structure with just agenda, skip internal pre-read or keep it minimal
+**"Claude research too generic"**: Focus on specific insights relevant to the actual meeting topic, not general platitudes
+
+## Examples
+
+See [examples/](examples/) for complete workflows:
+- [examples/project-decision.md](examples/project-decision.md) - Decision meeting prep with pre-read
+- [examples/sprint-planning.md](examples/sprint-planning.md) - Sprint planning meeting
+- [examples/executive-review.md](examples/executive-review.md) - Executive review prep
+- [examples/customer-meeting.md](examples/customer-meeting.md) - External meeting with customer (pre-read + agenda)
+

official-skills/notion-meeting-intelligence/evaluations/README.md

@@ -0,0 +1,101 @@
+# Meeting Intelligence Skill Evaluations
+
+Evaluation scenarios for testing the Meeting Intelligence skill across different Claude models.
+
+## Purpose
+
+These evaluations ensure the Meeting Intelligence skill:
+- Gathers context from Notion workspace
+- Enriches with Claude research appropriately
+- Creates both internal pre-reads and external agendas
+- Distinguishes between Notion facts and Claude insights
+- Works consistently across Haiku, Sonnet, and Opus
+
+## Evaluation Files
+
+### decision-meeting-prep.json
+Tests preparation for a decision-making meeting.
+
+**Scenario**: Prep for database migration decision meeting  
+**Key Behaviors**:
+- Searches Notion for migration context (specs, discussions, options)
+- Fetches 2-3 relevant pages
+- Enriches with Claude research (decision frameworks, migration best practices)
+- Creates comprehensive internal pre-read with recommendation
+- Creates clean, professional external agenda
+- Clearly distinguishes Notion facts from Claude insights
+- Cross-links both documents
+
+### status-meeting-prep.json
+Tests preparation for a status update or review meeting.
+
+**Scenario**: Prep for project status review  
+**Key Behaviors**:
+- Gathers project metrics and progress from Notion
+- Fetches relevant pages (roadmap, tasks, milestones)
+- Adds Claude context (industry benchmarks, best practices)
+- Creates internal pre-read with honest assessment
+- Creates external agenda with structured flow
+- Includes source citations using mention-page tags
+- Time-boxes agenda items
+
+## Running Evaluations
+
+1. Enable the `meeting-intelligence` skill
+2. Submit the query from the evaluation file
+3. Verify the skill searches Notion first (not Claude research)
+4. Check that TWO documents are created (internal + external)
+5. Verify Claude enrichment adds value without replacing Notion content
+6. Test with Haiku, Sonnet, and Opus
+
+## Expected Skill Behaviors
+
+Meeting Intelligence evaluations should verify:
+
+### Notion Context Gathering
+- Searches workspace for relevant context first
+- Fetches specific pages (not generic)
+- Extracts key information from Notion content
+- Cites sources using mention-page tags
+
+### Claude Research Integration
+- Adds industry context, frameworks, or best practices
+- Enrichment is relevant and valuable (not filler)
+- Clearly distinguishes Notion facts from Claude insights
+- Research complements (doesn't replace) Notion content
+
+### Two-Document Creation
+- **Internal Pre-Read**: Comprehensive, includes strategy, recommendations, detailed pros/cons
+- **External Agenda**: Professional, focused on meeting flow, no internal strategy
+- Both documents are clearly labeled
+- Documents are cross-linked
+
+### Document Quality
+- Pre-read follows structure: Overview → Background → Current Status → Context & Insights → Discussion Points
+- Agenda follows structure: Details → Objective → Agenda Items (with times) → Decisions → Actions → Resources
+- Titles include date or meeting context
+- Content is actionable and meeting-ready
+
+## Creating New Evaluations
+
+When adding Meeting Intelligence evaluations:
+
+1. **Test different meeting types** - Decision, status, brainstorm, 1:1, sprint planning, retrospective
+2. **Vary complexity** - Simple updates vs. complex strategic decisions
+3. **Test with/without Notion content** - Rich workspace vs. minimal existing pages
+4. **Verify enrichment value** - Is Claude research genuinely helpful?
+5. **Check internal/external distinction** - Is sensitive info kept in pre-read only?
+
+## Example Success Criteria
+
+**Good** (specific, testable):
+- "Creates TWO documents (internal pre-read + external agenda)"
+- "Internal pre-read marked 'INTERNAL ONLY' or 'For team only'"
+- "Cites at least 2-3 Notion pages using mention-page tags"
+- "Agenda includes time allocations for each section"
+- "Claude enrichment includes decision frameworks or best practices"
+
+**Bad** (vague, untestable):
+- "Creates meeting materials"
+- "Gathers context effectively"
+- "Prepares well"

official-skills/notion-meeting-intelligence/evaluations/decision-meeting-prep.json

@@ -0,0 +1,35 @@
+{
+  "name": "Decision Meeting Preparation",
+  "skills": ["meeting-intelligence"],
+  "query": "Prep for tomorrow's meeting where we need to decide on our database migration approach. Create both an internal pre-read for the team and an agenda for the meeting.",
+  "expected_behavior": [
+    "Step 1: Uses Notion:notion-search to find context about database migration (project pages, technical specs, previous discussions, options analysis)",
+    "Step 2: Fetches at least 2-3 relevant pages using Notion:notion-fetch to gather information from Notion",
+    "Step 3: Identifies the decision to be made and available options from fetched Notion content",
+    "Step 4: Enriches with Claude research - adds decision-making frameworks (e.g., cost-benefit analysis, risk assessment), technical context for migration approaches, best practices for database migrations",
+    "Step 5: Distinguishes Notion facts from Claude insights in synthesis",
+    "Step 6: Creates INTERNAL PRE-READ using Notion:notion-create-pages with title like 'INTERNAL: Database Migration Decision - Pre-Read - [Date]'",
+    "Step 6a: Internal pre-read includes: Meeting overview, background context (from Notion), current status and technical details, context & insights (from Claude research on migration best practices), decision options with detailed pros/cons, recommendation with rationale, what we need from meeting",
+    "Step 6b: Internal pre-read marked clearly as 'INTERNAL ONLY' or 'For team only'",
+    "Step 7: Creates EXTERNAL AGENDA using Notion:notion-create-pages with title like 'Meeting Agenda: Database Migration Decision - [Date]'",
+    "Step 7a: External agenda includes: Meeting details, objective (clear decision to make), agenda items with time allocations, discussion topics, decisions needed, action items section (empty), related resources with link to pre-read",
+    "Step 7b: External agenda is clean, professional, focused (no internal strategy or detailed pros/cons)",
+    "Step 8: Links both documents together (agenda mentions pre-read, pre-read mentions agenda)",
+    "Both documents link to source pages using <mention-page url='...'>"
+  ],
+  "success_criteria": [
+    "TWO documents are created (internal pre-read + external agenda), not just one",
+    "Internal pre-read is comprehensive with: Notion context + Claude insights + detailed pros/cons + recommendation",
+    "Internal pre-read is clearly marked 'INTERNAL' or 'For team only'",
+    "External agenda is professional, structured, focused on meeting flow (not internal strategy)",
+    "Claude enrichment is present and adds value (decision frameworks, migration best practices, risk patterns)",
+    "Notion facts are clearly sourced, Claude insights are distinguished",
+    "At least 2-3 Notion source pages are cited using mention-page tags",
+    "Internal pre-read follows structure from SKILL.md Step 5 (Meeting Overview → Background → Current Status → Context & Insights → Key Discussion Points → What We Need)",
+    "External agenda follows structure from SKILL.md Step 6 (Meeting Details → Objective → Agenda Items → Discussion Topics → Decisions Needed → Action Items → Related Resources)",
+    "Documents are cross-linked (pre-read mentions agenda, agenda mentions pre-read)",
+    "Meeting date is included in both titles",
+    "Uses correct tool names (Notion:notion-search, Notion:notion-fetch, Notion:notion-create-pages for BOTH documents)"
+  ]
+}
+

official-skills/notion-meeting-intelligence/evaluations/status-meeting-prep.json

@@ -0,0 +1,35 @@
+{
+  "name": "Status Update Meeting Preparation",
+  "skills": ["meeting-intelligence", "task-manager"],
+  "query": "Prep for Friday's project status meeting on the Mobile App Redesign project. Create both an internal pre-read and an external agenda.",
+  "expected_behavior": [
+    "Step 1: Uses Notion:notion-search to find Mobile App Redesign project page",
+    "Step 2: Fetches project page using Notion:notion-fetch to get current status and context",
+    "Step 3: Uses Notion:notion-search to find tasks database",
+    "Step 4: Queries task database using Notion:notion-query-data-sources for project tasks (WHERE Project = 'Mobile App Redesign')",
+    "Step 5: Analyzes task data: calculates completion %, identifies completed work, in-progress items, and blockers",
+    "Step 6: Enriches with Claude research - adds project management insights (velocity trends, risk patterns, common project pitfalls), suggests discussion frameworks if risks identified, provides context on timeline implications",
+    "Step 7: Creates INTERNAL PRE-READ using Notion:notion-create-pages with title 'INTERNAL: Mobile App Redesign Status - Pre-Read - [Date]'",
+    "Step 7a: Internal pre-read includes: Project overview, current status with metrics (from Notion/tasks), progress summary with specifics, context & insights (Claude research on project health patterns), honest assessment of challenges/risks, what we need from meeting",
+    "Step 7b: Internal pre-read contains detailed metrics, blockers, and strategic considerations",
+    "Step 8: Creates EXTERNAL AGENDA using Notion:notion-create-pages with title 'Meeting Agenda: Mobile App Redesign Status Update - [Date]'",
+    "Step 8a: External agenda uses Status Update structure: Meeting Details → Objective → Agenda Items (timed) → Discussion Topics → Action Items",
+    "Step 8b: External agenda is concise, professional, focuses on meeting flow (summary-level metrics only)",
+    "Step 9: Links both documents together",
+    "Both documents link to project page and task database using <mention-page> and <mention-database>"
+  ],
+  "success_criteria": [
+    "TWO documents are created (internal pre-read + external agenda)",
+    "Internal pre-read contains: Detailed metrics from task query, honest assessment of blockers/risks, Claude insights on project health patterns, strategic considerations",
+    "Internal pre-read is marked 'INTERNAL' or 'For team only'",
+    "External agenda is professional status update format with: Overall status, progress summary (high-level), upcoming work, discussion topics, action items section",
+    "External agenda does NOT contain detailed risk analysis or internal strategic discussion (that's in pre-read)",
+    "Progress metrics are accurate based on Notion:notion-query-data-sources results (e.g., X complete, Y in progress, Z blocked)",
+    "Blockers identified from task query are included in internal pre-read with full context",
+    "Claude enrichment adds value (project management insights, risk patterns, velocity analysis)",
+    "Links to project page and task database using mention tags",
+    "Documents are cross-linked for easy navigation",
+    "Uses correct tool names (Notion:notion-search, Notion:notion-fetch, Notion:notion-query-data-sources, Notion:notion-create-pages for BOTH documents)"
+  ]
+}
+

official-skills/notion-meeting-intelligence/examples/customer-meeting.md

@@ -0,0 +1,125 @@
+# Example: Customer Meeting Prep
+
+**User Request**: "Prep for sales meeting with Acme Corp on Thursday"
+
+## Workflow
+
+### 1. Search Customer Info
+```
+Notion:notion-search
+query: "Acme Corp"
+```
+
+Found:
+- CRM notes from initial call
+- Product demo feedback
+- Pricing proposal
+- Competitor analysis
+
+### 2. Fetch Details
+```
+Notion:notion-fetch (4 pages)
+```
+
+**Key context**:
+- **Company**: 500-person fintech startup, Series B
+- **Pain Points**: Manual workflows, data silos, scaling issues
+- **Decision Makers**: CTO (technical), VP Product (user needs), CFO (budget)
+- **Timeline**: Need solution by Q1
+- **Budget**: $50-75K/year range
+- **Competition**: Evaluating us vs. Competitor A and Competitor B
+
+### 3. Add Research Context
+Claude research added:
+- Fintech industry compliance requirements
+- Common integration needs for financial products
+- Typical procurement processes for Series B companies
+
+### 4. Create Internal Pre-Read
+```
+Notion:notion-create-pages
+pages: [{
+  properties: {
+    title: "Acme Corp Meeting - Pre-Read (Internal)"
+  },
+  content: "# Acme Corp Meeting - Pre-Read (Internal)
+
+## Company Overview
+**Company**: Acme Corp (500-person fintech, Series B)
+**Decision Makers**: CTO, VP Product, CFO
+Source: <mention-page url='...'>CRM Notes</mention-page>
+
+## Their Pain Points → Our Solutions
+- Manual workflows → Workflow automation
+- Data silos → API integrations
+- Scaling issues → Enterprise features
+
+## Competitive Position
+**Our advantages over Competitor A/B**:
+- Better integration ecosystem (Stripe, Plaid)
+- Stronger compliance features
+- Faster implementation (4 weeks vs 12 weeks)
+
+## Pricing Strategy
+Recommend: $60K/year (mid-range of their budget)
+
+## Potential Objections & Responses
+..."
+}]
+```
+
+### 5. Create Meeting Agenda
+```
+Notion:notion-create-pages
+pages: [{
+  properties: {
+    title: "Acme Corp - Product Demo & Q&A"
+  },
+  content: "# Acme Corp - Product Demo & Q&A
+
+## Meeting Details
+**Date**: Thursday, Oct 17, 2025 @ 2pm PST
+**Attendees**: CTO, VP Product, CFO (Acme) | Sales Lead, Solutions Engineer (Us)
+**Duration**: 60 minutes
+
+## Objective
+Demonstrate how our platform solves Acme's workflow automation and integration challenges.
+
+## Agenda
+
+**1. Introductions** (5 min)
+
+**2. Understand Current Workflow** (10 min)
+- Current pain points
+- Integration requirements
+- Success criteria
+
+**3. Product Demo** (25 min)
+- Workflow automation capabilities
+- API integrations (Stripe, Plaid)
+- Security & compliance features
+
+**4. Pricing & Implementation** (10 min)
+
+**5. Next Steps** (10 min)
+"
+}]
+```
+
+### 6. Link Resources
+Connected agenda to CRM page, pricing sheet, and technical integration docs.
+
+## Outputs
+
+**Internal Pre-Read**: Full context for sales team
+**Customer Agenda**: Professional meeting structure
+**Both in Notion** with links to supporting materials
+
+## Key Success Factors
+- Understood customer's specific pain points
+- Researched industry context (fintech compliance)
+- Mapped features to their needs
+- Prepared competitive differentiators
+- Structured demo around their use cases
+- Pre-planned objection responses
+- Clear next steps in agenda

official-skills/notion-meeting-intelligence/examples/executive-review.md

@@ -0,0 +1,78 @@
+# Example: Executive Review Prep
+
+**User Request**: "Prep for quarterly executive review on Friday"
+
+## Workflow
+
+### 1. Search for Context
+```
+Notion:notion-search
+query: "Q4 objectives" + "KPIs" + "quarterly results"
+```
+
+Found:
+- Q4 OKRs and progress
+- Product metrics dashboard
+- Engineering velocity reports
+- Customer feedback summary
+
+### 2. Fetch & Analyze
+```
+Notion:notion-fetch (5 pages)
+```
+
+**Key metrics**:
+- **Revenue**: $2.4M ARR (96% of Q4 target)
+- **Customer Growth**: 145 new customers (exceeds 120 target)
+- **Churn**: 3.2% (below 5% target)
+- **Product**: 3 major features shipped, 2 in beta
+- **Engineering**: 94% uptime (above 95% SLA)
+
+### 3. Add Claude Research Context
+Added context on:
+- Industry benchmarks for SaaS metrics
+- Typical Q4 sales patterns
+- Best practices for executive presentations
+
+### 4. Create Pre-Read (Internal)
+```
+Notion:notion-create-pages
+title: "Q4 Review - Pre-Read (Internal)"
+```
+
+**Pre-read sections**:
+- **Executive Summary**: Strong quarter, missed revenue by 4% but exceeded customer growth
+- **Detailed Metrics**: All KPIs with trend lines
+- **Wins**: Product launches, key customer acquisitions
+- **Challenges**: Sales pipeline conversion, engineering hiring
+- **Q1 Preview**: Strategic priorities
+
+### 5. Create Presentation Agenda
+```
+Notion:notion-create-pages
+title: "Q4 Executive Review - Agenda"
+```
+
+**Agenda** (90 min):
+- Q4 Results Overview (15 min)
+- Revenue & Growth Deep Dive (20 min)
+- Product & Engineering Update (20 min)
+- Customer Success Highlights (15 min)
+- Q1 Strategic Plan (15 min)
+- Discussion & Questions (15 min)
+
+### 6. Link Supporting Docs
+Connected to OKRs, metrics dashboards, and Q1 planning docs.
+
+## Outputs
+
+**Internal Pre-Read**: Comprehensive context with honest assessment
+**Executive Agenda**: Structured 90-min presentation
+**Both in Notion** with links to supporting data
+
+## Key Success Factors
+- Synthesized data from multiple sources (OKRs, metrics, feedback)
+- Added industry context and benchmarks
+- Created honest internal assessment (not just wins)
+- Structured agenda with time allocations
+- Linked to source data for drill-down during Q&A

official-skills/notion-meeting-intelligence/examples/project-decision.md

@@ -0,0 +1,431 @@
+# Example: Project Decision Meeting Prep
+
+## User Request
+
+> "Prep for tomorrow's architecture meeting where we need to decide on database migration strategy"
+
+## Workflow Execution
+
+### Step 1: Search for Context
+
+```
+Notion:notion-search
+query: "database migration"
+query_type: "internal"
+teamspace_id: "engineering-teamspace-id"
+filters: {
+  created_date_range: {
+    start_date: "2024-01-01"
+  }
+}
+```
+
+**Results Found:**
+- "Database Migration Proposal" (Engineering)
+- "Current Database Performance Issues" (Engineering)
+- "Migration Options Analysis" (Architecture)
+- "Previous Migration Post-mortem" (Engineering)
+
+### Step 2: Fetch Relevant Pages
+
+```
+Notion:notion-fetch
+id: "database-migration-proposal-page-id"
+```
+
+**Extracted**: Proposes migrating from MongoDB to PostgreSQL, outlines timeline and risks
+
+```
+Notion:notion-fetch
+id: "database-performance-issues-page-id"
+```
+
+**Extracted**: Current pain points - slow queries, schema flexibility issues, transaction limitations
+
+```
+Notion:notion-fetch
+id: "migration-options-analysis-page-id"
+```
+
+**Extracted**: Three options analyzed:
+1. Stay on MongoDB with optimizations
+2. Migrate to PostgreSQL
+3. Hybrid approach (MongoDB + PostgreSQL)
+
+```
+Notion:notion-fetch
+id: "previous-migration-postmortem-page-id"
+```
+
+**Extracted**: Lessons from 2023 Redis migration - importance of rollback plan, testing strategy
+
+### Step 3: Synthesize Pre-Read
+
+**Key Information Identified:**
+- **Problem**: MongoDB performance degrading, schema flexibility causing data consistency issues
+- **Options**: Three approaches with different trade-offs
+- **Recommendation**: PostgreSQL migration favored by engineering team
+- **Concerns**: Downtime requirements, data migration complexity, application changes needed
+- **Historical context**: Previous migration took 6 weeks, had rollback issues
+
+### Step 4: Create Meeting Agenda
+
+```
+Notion:notion-create-pages
+
+parent: { page_id: "meetings-parent-id" }
+
+pages: [{
+  properties: {
+    "title": "Architecture Decision: Database Migration Strategy - Oct 15, 2025"
+  },
+  content: "[Decision meeting agenda]"
+}]
+```
+
+**Agenda Created:**
+
+```markdown
+# Architecture Decision: Database Migration Strategy
+
+## Meeting Details
+**Date & Time**: October 15, 2025 at 2:00 PM  
+**Duration**: 90 minutes  
+**Location**: Conference Room B / Zoom  
+**Facilitator**: Sarah Chen (Engineering Lead)  
+**Attendees**:
+- Sarah Chen (Engineering Lead)
+- David Kim (CTO)
+- Alice Wang (Backend Team Lead)
+- Bob Martinez (DevOps Lead)
+- Carol Johnson (Product Director)
+
+## Pre-Read Summary
+
+### Background
+
+Our MongoDB database is experiencing performance degradation as we scale. Query response times have increased from 50ms to 400ms average over the past 6 months. The schema-less nature that initially provided flexibility is now causing data consistency issues and making application logic more complex.
+
+**Source**: <mention-page url="...">Current Database Performance Issues</mention-page>
+
+### Current Situation
+
+**Performance metrics**:
+- Average query time: 400ms (was 50ms 6 months ago)
+- p95 query time: 1.2s (was 200ms)
+- Database size: 500GB (growing 20GB/month)
+- Connection pool exhaustion during peak traffic
+
+**Technical debt**:
+- 15+ application-layer validation rules compensating for lack of schema
+- Complex data migration scripts for schema changes
+- Limited transaction support causing race conditions
+
+**Source**: <mention-page url="...">Database Migration Proposal</mention-page>
+
+### Historical Context
+
+We successfully migrated from Redis to Memcached in 2023, which took 6 weeks. Key learnings:
+- Underestimated application code changes (3 weeks instead of 1 week)
+- Rollback plan was crucial when we discovered compatibility issues
+- Parallel running period (dual writes) was essential for safe migration
+
+**Source**: <mention-page url="...">Previous Migration Post-mortem</mention-page>
+
+## Decision Required
+
+**Question**: Which database migration strategy should we adopt?
+
+**Timeline**: Need decision by end of week to include in Q4 planning
+
+**Impact**: 
+- Engineering team (4-8 weeks of work)
+- Application architecture
+- Operations & monitoring
+- Future feature development velocity
+
+## Options Analysis
+
+### Option A: Stay on MongoDB with Optimizations
+
+**Description**: Invest in MongoDB performance tuning, add indexes, upgrade to latest version, implement better query patterns.
+
+**Pros**:
+- ✅ No migration complexity
+- ✅ Team familiar with MongoDB
+- ✅ Can implement immediately
+- ✅ Lower risk
+- ✅ Estimated 2 weeks effort
+
+**Cons**:
+- ❌ Doesn't solve fundamental schema flexibility issues
+- ❌ Still limited transaction support
+- ❌ Performance improvements may be temporary
+- ❌ Continues technical debt accumulation
+
+**Cost/Effort**: 2 weeks engineering + $5K/year additional MongoDB infrastructure
+
+**Risk**: Medium - Improvements may not be sufficient
+
+**Source**: <mention-page url="...">Migration Options Analysis</mention-page>
+
+### Option B: Migrate to PostgreSQL
+
+**Description**: Full migration from MongoDB to PostgreSQL. Redesign schema with proper constraints, implement dual-write period, then cut over.
+
+**Pros**:
+- ✅ Solves schema consistency issues
+- ✅ Full ACID transactions
+- ✅ Better performance for relational queries
+- ✅ Lower long-term complexity
+- ✅ Industry standard, easier hiring
+
+**Cons**:
+- ❌ High migration effort (6-8 weeks)
+- ❌ Requires schema redesign
+- ❌ Application code changes extensive
+- ❌ Risk of data loss during migration
+- ❌ Downtime required (4-6 hours estimated)
+
+**Cost/Effort**: 8 weeks engineering + $8K migration costs - $15K/year MongoDB savings = net $7K/year savings
+
+**Risk**: High - Complex migration, application changes required
+
+**Recommendation**: ✅ **Favored by engineering team**
+
+**Source**: <mention-page url="...">Database Migration Proposal</mention-page>
+
+### Option C: Hybrid Approach
+
+**Description**: Keep MongoDB for document-heavy data (logs, analytics), migrate transactional data to PostgreSQL. Run both databases.
+
+**Pros**:
+- ✅ Phased migration (lower risk)
+- ✅ Use best tool for each data type
+- ✅ Can migrate incrementally
+- ✅ Smaller initial scope (4 weeks)
+
+**Cons**:
+- ❌ Increased operational complexity
+- ❌ Two databases to maintain
+- ❌ Data consistency between databases challenging
+- ❌ Higher infrastructure costs
+- ❌ Complex application logic
+
+**Cost/Effort**: 4 weeks initial + ongoing complexity + $10K/year additional infrastructure
+
+**Risk**: Medium - Operational complexity increases
+
+**Source**: <mention-page url="...">Migration Options Analysis</mention-page>
+
+### Option D: Do Nothing
+
+**Description**: Accept current performance and continue with MongoDB as-is.
+
+**Implications**:
+- Performance continues to degrade
+- Technical debt increases
+- Feature development slows
+- Customer experience suffers
+- Eventually forced into emergency migration
+
+**Not recommended**
+
+## Discussion Topics
+
+### Technical Feasibility
+1. Can we achieve < 4 hours downtime for Option B?
+2. What's the rollback plan if PostgreSQL migration fails?
+3. How do we handle data migration for 500GB?
+4. Schema design - what constraints do we need?
+
+### Business Impact
+5. What's the customer impact of 4-6 hours downtime?
+6. Can we schedule migration during low-traffic period?
+7. How does this affect Q4 feature roadmap?
+8. Cost-benefit analysis over 2-year horizon?
+
+### Risk Management
+9. What are the biggest risks with Option B?
+10. How do we test thoroughly before cutover?
+11. What's the rollback procedure and time?
+12. Do we have necessary expertise on team?
+
+### Timeline & Resources
+13. Can we allocate 2 engineers full-time for 8 weeks?
+14. Do we need external consultants?
+15. What's the impact on other Q4 projects?
+16. When could we realistically complete this?
+
+## Decision Framework
+
+**Evaluation criteria**:
+1. **Performance improvement**: Will this solve our performance issues?
+2. **Technical debt**: Does this reduce or increase complexity?
+3. **Risk**: What's the probability and impact of failure?
+4. **Cost**: Total cost of ownership (effort + infrastructure)
+5. **Timeline**: Can we complete in Q4?
+6. **Reversibility**: Can we roll back if needed?
+
+**Decision makers**:
+- Primary: David Kim (CTO)
+- Consulted: Sarah Chen (Engineering), Bob Martinez (DevOps)
+- Informed: Product, Executive team
+
+## Decision
+
+*[To be filled during meeting]*
+
+**Selected Option**: ___________________
+
+**Rationale**:
+
+**Timeline**:
+
+**Owner**: ___________________
+
+**Success Criteria**:
+
+## Action Items
+
+*[To be filled during meeting]*
+
+- [ ] [Action item] - @[Owner] - Due: [Date]
+- [ ] [Action item] - @[Owner] - Due: [Date]
+
+## Next Steps
+
+**Immediate**:
+- Document decision rationale
+- Create detailed implementation plan
+- Schedule kickoff meeting
+
+**Follow-up meeting**: [Date] to review migration plan
+
+## Related Resources
+
+### Primary Sources
+- <mention-page url="...">Database Migration Proposal</mention-page>
+- <mention-page url="...">Current Database Performance Issues</mention-page>
+- <mention-page url="...">Migration Options Analysis</mention-page>
+- <mention-page url="...">Previous Migration Post-mortem</mention-page>
+
+### Supporting Documents
+- MongoDB performance metrics dashboard
+- PostgreSQL evaluation results
+- Cost analysis spreadsheet
+```
+
+### Step 5: Share Agenda
+
+```
+Notion:notion-create-comment
+parent: { page_id: "agenda-page-id" }
+rich_text: [{
+  type: "text",
+  text: { content: "📋 Meeting agenda ready! Please review the pre-read before tomorrow's meeting. cc: @Sarah @David @Alice @Bob @Carol" }
+}]
+```
+
+## Summary Provided to User
+
+```markdown
+## Meeting Prep Complete ✅
+
+### Meeting Details
+- **Topic**: Database Migration Strategy Decision
+- **Date**: October 15, 2025 at 2:00 PM
+- **Duration**: 90 minutes
+- **Attendees**: 5 (Engineering leads + CTO + Product)
+
+### Agenda Created
+<mention-page url="...">Architecture Decision: Database Migration Strategy</mention-page>
+
+### Pre-Read Summary
+
+**Problem**: MongoDB performance degrading (50ms → 400ms queries), schema flexibility causing issues
+
+**Decision needed**: Choose between:
+1. Stay on MongoDB (optimizations) - 2 weeks, low risk
+2. Migrate to PostgreSQL - 8 weeks, high value, high risk ✅ Recommended
+3. Hybrid approach - 4 weeks, medium complexity
+4. Do nothing - Not recommended
+
+**Recommendation**: Engineering team favors PostgreSQL migration
+
+### Key Information Included
+
+✅ **Background context** from 4 relevant pages
+✅ **Options analysis** with pros/cons for each
+✅ **Cost-benefit** breakdown
+✅ **Risk assessment** for each option
+✅ **Discussion topics** (16 questions organized by theme)
+✅ **Decision framework** with evaluation criteria
+✅ **Historical context** from previous migration
+✅ **Empty sections** for decision and action items
+
+### Discussion Topics Prepared
+
+**Technical** (4 questions):
+- Downtime achievability
+- Rollback planning
+- Data migration approach
+- Schema design
+
+**Business** (4 questions):
+- Customer impact
+- Scheduling
+- Roadmap impact
+- Cost analysis
+
+**Risk** (4 questions):
+- Risk identification
+- Testing strategy
+- Rollback procedure
+- Expertise availability
+
+**Resources** (4 questions):
+- Team allocation
+- External help needs
+- Project trade-offs
+- Timeline realism
+
+### Success Factors
+
+1. **Comprehensive research**: 4 relevant pages analyzed
+2. **Clear options**: Pros/cons for each approach
+3. **Structured discussion**: 16 questions organized by theme
+4. **Decision framework**: Clear criteria for evaluation
+5. **Historical context**: Lessons from previous migration
+6. **Ready for outcomes**: Sections prepared for decision and actions
+
+**Meeting is well-prepared for productive decision-making! 📊**
+```
+
+## Key Features Demonstrated
+
+### Context Gathering
+- **Targeted search**: Engineering teamspace, recent documents
+- **Multiple perspectives**: Performance data, proposals, analysis, historical lessons
+- **Comprehensive synthesis**: Combined technical, business, and historical context
+
+### Options Analysis
+- **Structured comparison**: Pros/cons for each option
+- **Cost-benefit**: Effort and infrastructure costs included
+- **Risk assessment**: Probability and impact noted
+- **Recommendation**: Clear engineering preference stated
+
+### Decision Support
+- **Discussion topics**: 16 questions organized by theme
+- **Decision framework**: Evaluation criteria defined
+- **Decision makers**: Roles and responsibilities clear
+- **Outcome capture**: Sections ready for decision and actions
+
+### Meeting Structure
+- **Pre-read**: Comprehensive background (can be read in 10 minutes)
+- **Options**: Clear comparison for quick decision
+- **Discussion**: Structured topics prevent rambling
+- **Capture**: Templates for decision and actions
+
+Perfect for: Architecture decisions, technical trade-offs, strategic choices
+

official-skills/notion-meeting-intelligence/examples/sprint-planning.md

@@ -0,0 +1,80 @@
+# Example: Sprint Planning Meeting Prep
+
+**User Request**: "Prepare for tomorrow's sprint planning meeting"
+
+## Workflow
+
+### 1. Search for Context
+```
+Notion:notion-search
+query: "sprint planning" + "product backlog"
+teamspace_id: "engineering-team"
+```
+
+Found:
+- Last sprint retrospective
+- Product backlog (prioritized)
+- Current sprint progress
+- Team capacity notes
+
+### 2. Fetch Details
+```
+Notion:notion-fetch (4 pages)
+```
+
+**Key context**:
+- **Last Sprint**: Completed 32/35 story points (91%)
+- **Velocity**: Consistent 30-35 points over last 3 sprints
+- **Team**: 5 engineers, 1 on vacation next sprint (80% capacity)
+- **Top Backlog Items**: User auth improvements, API performance, mobile responsive fixes
+
+### 3. Query Current Sprint Tasks
+```
+Notion:notion-query-data-sources
+query: "SELECT * FROM tasks WHERE Sprint = 'Sprint 24' AND Status != 'Done'"
+```
+
+3 tasks carrying over (technical debt items)
+
+### 4. Create Pre-Read (Internal)
+```
+Notion:notion-create-pages
+title: "Sprint 25 Planning - Pre-Read (Internal)"
+```
+
+**Pre-read included**:
+- Sprint 24 summary (velocity, what carried over)
+- Team capacity for Sprint 25
+- Top backlog candidates with story points
+- Technical dependencies
+- Risk items (auth changes need QA time)
+
+### 5. Create Agenda
+```
+Notion:notion-create-pages  
+title: "Sprint 25 Planning - Agenda"
+```
+
+**Agenda**:
+- Review Sprint 24 completion (5 min)
+- Discuss carryover items (5 min)
+- Review capacity (28 points available)
+- Select backlog items (30 min)
+- Identify dependencies & risks (10 min)
+- Confirm commitments (10 min)
+
+### 6. Link Documents
+Cross-linked pre-read and agenda, referenced last retro and backlog.
+
+## Output Summary
+
+**Internal Pre-Read**: Team context, capacity, blockers
+**External Agenda**: Meeting structure, discussion topics
+**Both saved to Notion** and linked to project pages
+
+## Key Success Factors
+- Gathered sprint history for velocity trends
+- Calculated realistic capacity (account for PTO)
+- Identified carryover items upfront
+- Pre-read gave team context before meeting
+- Agenda kept meeting focused and timeboxed

official-skills/notion-meeting-intelligence/reference/brainstorming-template.md

@@ -0,0 +1,81 @@
+# Brainstorming Meeting Template
+
+Use this template for creative ideation and brainstorming sessions.
+
+```markdown
+# [Topic] Brainstorming - [Date]
+
+## Meeting Details
+**Date**: [Date]
+**Facilitator**: [Name]
+**Note-taker**: [Name]
+**Attendees**: [List]
+
+## Objective
+
+[Clear statement of what we're brainstorming]
+
+**Success looks like**: [How we'll know brainstorming was successful]
+
+## Background & Context
+
+[Context from research - 2-3 paragraphs]
+
+**Related Pages**:
+- <mention-page url="...">Context Page 1</mention-page>
+- <mention-page url="...">Context Page 2</mention-page>
+
+## Constraints
+
+- [Constraint]
+- [Constraint]
+- [Constraint]
+
+## Seed Ideas
+
+[Starting ideas from research to spark discussion]:
+
+1. **[Idea]**: [Brief description]
+2. **[Idea]**: [Brief description]
+
+## Ground Rules
+
+- No criticism during ideation
+- Build on others' ideas
+- Quantity over quality initially
+- Wild ideas welcome
+
+## Brainstorming Notes
+
+### Ideas Generated
+
+[To be filled during meeting]
+
+1. [Idea with brief description]
+2. [Idea with brief description]
+
+### Themes/Patterns
+
+[Groupings that emerge]
+
+## Evaluation
+
+[If time permits, evaluate top ideas]
+
+### Top Ideas
+
+| Idea | Feasibility | Impact | Effort | Score |
+|------|-------------|---------|--------|-------|
+| [Idea] | [H/M/L] | [H/M/L] | [H/M/L] | [#] |
+
+## Next Steps
+
+- [ ] [Action to explore idea]
+- [ ] [Action to prototype]
+- [ ] [Action to research]
+
+## Follow-up
+
+**Next meeting**: [Date to reconvene]
+```
+

official-skills/notion-meeting-intelligence/reference/decision-meeting-template.md

@@ -0,0 +1,94 @@
+# Decision Meeting Template
+
+Use this template when you need to make an important decision with your team.
+
+```markdown
+# [Decision Topic] - [Date]
+
+## Meeting Details
+**Date & Time**: [Date and time]
+**Duration**: [Length]
+**Attendees**: [List of attendees with roles]
+**Location**: [Physical location or video link]
+**Facilitator**: [Name]
+
+## Pre-Read Summary
+
+### Background
+[2-3 sentences providing context from related project pages]
+
+**Related Pages**:
+- <mention-page url="...">Project Overview</mention-page>
+- <mention-page url="...">Previous Discussion</mention-page>
+
+### Current Situation
+[What brings us to this decision point]
+
+## Decision Required
+
+**Question**: [Clear statement of decision needed]
+
+**Timeline**: [When decision needs to be made]
+
+**Impact**: [Who/what is affected by this decision]
+
+## Options Analysis
+
+### Option A: [Name]
+**Description**: [What this option entails]
+
+**Pros**:
+- [Advantage]
+- [Advantage]
+
+**Cons**:
+- [Disadvantage]
+- [Disadvantage]
+
+**Cost/Effort**: [Estimate]
+**Risk**: [Risk assessment]
+
+### Option B: [Name]
+[Repeat structure]
+
+### Option C: Do Nothing
+**Description**: What happens if we don't decide
+**Implications**: [Consequences]
+
+## Recommendation
+
+[If there is a recommended option, state it with rationale]
+
+## Discussion Topics
+
+1. [Topic to discuss]
+2. [Clarification needed on]
+3. [Trade-offs to consider]
+
+## Decision Framework
+
+**Criteria for evaluation**:
+- [Criterion 1]
+- [Criterion 2]
+- [Criterion 3]
+
+## Decision
+
+[To be filled during meeting]
+
+**Selected Option**: [Option chosen]
+**Rationale**: [Why]
+**Owner**: [Who will implement]
+**Timeline**: [When]
+
+## Action Items
+
+- [ ] [Action] - @[Owner] - Due: [Date]
+- [ ] [Action] - @[Owner] - Due: [Date]
+
+## Follow-up
+
+**Next review**: [Date]
+**Success metrics**: [How we'll know this worked]
+```
+

official-skills/notion-meeting-intelligence/reference/one-on-one-template.md

@@ -0,0 +1,58 @@
+# 1:1 Meeting Template
+
+Use this template for manager/report one-on-one meetings.
+
+```markdown
+# 1:1: [Manager] & [Report] - [Date]
+
+## Meeting Details
+**Date**: [Date]
+**Last meeting**: <mention-page url="...">Previous 1:1</mention-page>
+
+## Agenda
+
+### [Report]'s Topics
+1. [Topic to discuss]
+2. [Question or concern]
+
+### [Manager]'s Topics
+1. [Topic to cover]
+2. [Feedback or update]
+
+## Discussion Notes
+
+### [Topic 1]
+[Discussion points]
+
+**Action items**:
+- [ ] [Action] - @[Owner]
+
+### [Topic 2]
+[Discussion points]
+
+## Career Development
+
+**Current focus**: [Development goal]
+**Progress**: [Update on progress]
+
+## Feedback
+
+**What's going well**:
+- [Positive feedback]
+
+**Areas for growth**:
+- [Developmental feedback]
+
+## Action Items
+
+- [ ] [Action] - @[Report] - Due: [Date]
+- [ ] [Action] - @[Manager] - Due: [Date]
+
+## Next Meeting
+
+**Date**: [Date]
+**Topics to cover**:
+- [Carry-over topic]
+- [Upcoming topic]
+```
+

official-skills/notion-meeting-intelligence/reference/retrospective-template.md

@@ -0,0 +1,58 @@
+# Retrospective Template
+
+Use this template for sprint retrospectives and team retrospectives.
+
+```markdown
+# Sprint [#] Retrospective - [Date]
+
+## Meeting Details
+**Date**: [Date]
+**Team**: [Team]
+**Sprint**: [Sprint dates]
+**Facilitator**: [Name]
+
+## Sprint Summary
+
+**Sprint Goal**: [Goal]
+**Goal Met**: Yes / Partially / No
+
+**Completed**: [#] points
+**Velocity**: [#] points
+**Planned**: [#] points
+
+## Pre-Read
+
+**Sprint Metrics**:
+- Tasks completed: [#]
+- Tasks carried over: [#]
+- Bugs found: [#]
+- Blockers encountered: [#]
+
+## Discussion
+
+### What Went Well (Keep)
+
+[Team input during meeting]
+
+### What Didn't Go Well (Stop)
+
+[Team input during meeting]
+
+### What To Try (Start)
+
+[Team input during meeting]
+
+### Shout-outs
+
+[Team recognition]
+
+## Action Items
+
+- [ ] [Improvement to implement] - @[Owner] - Due: [Date]
+- [ ] [Process change] - @[Owner] - Due: [Date]
+
+## Follow-up
+
+**Review actions in**: [Next retro date]
+```
+

official-skills/notion-meeting-intelligence/reference/sprint-planning-template.md

@@ -0,0 +1,68 @@
+# Sprint Planning Template
+
+Use this template for agile sprint planning meetings.
+
+```markdown
+# Sprint [#] Planning - [Date]
+
+## Meeting Details
+**Date**: [Date]
+**Team**: [Team name]
+**Sprint Duration**: [Dates]
+
+## Sprint Goal
+
+[Clear statement of what this sprint aims to accomplish]
+
+## Capacity
+
+| Team Member | Availability | Capacity (points) |
+|-------------|--------------|-------------------|
+| [Name] | [%] | [#] |
+| **Total** | | [#] |
+
+## Backlog Review
+
+### High Priority Items
+
+[From product backlog, linked from task database]
+
+- <mention-page url="...">Task 1</mention-page> - [Points]
+- <mention-page url="...">Task 2</mention-page> - [Points]
+
+## Sprint Backlog
+
+### Committed Items
+
+- [x] <mention-page url="...">Task</mention-page> - [Points] - @[Owner]
+- [ ] <mention-page url="...">Task</mention-page> - [Points] - @[Owner]
+
+**Total committed**: [Points]
+
+### Stretch Goals
+
+- [ ] <mention-page url="...">Task</mention-page> - [Points]
+
+## Dependencies & Risks
+
+**Dependencies**:
+- [Dependency]
+
+**Risks**:
+- [Risk]
+
+## Definition of Done
+
+- [ ] Code complete and reviewed
+- [ ] Tests written and passing
+- [ ] Documentation updated
+- [ ] Deployed to staging
+- [ ] QA approved
+
+## Next Steps
+
+- Team begins sprint work
+- Daily standups at [Time]
+- Sprint review on [Date]
+```
+

official-skills/notion-meeting-intelligence/reference/status-update-template.md

@@ -0,0 +1,74 @@
+# Status Update Meeting Template
+
+Use this template for regular project status updates and check-ins.
+
+```markdown
+# [Project Name] Status Update - [Date]
+
+## Meeting Details
+**Date**: [Date and time]
+**Attendees**: [List]
+**Project**: <mention-page url="...">Project Page</mention-page>
+
+## Executive Summary
+
+**Status**: 🟢 On Track / 🟡 At Risk / 🔴 Behind
+
+**Progress**: [Percentage] complete
+**Timeline**: [Status vs original plan]
+
+## Progress Since Last Meeting
+
+### Completed
+- [Accomplishment with specifics]
+- [Accomplishment with specifics]
+
+### In Progress
+- [Work item and status]
+- [Work item and status]
+
+## Metrics
+
+| Metric | Current | Target | Status |
+|--------|---------|--------|--------|
+| [Metric] | [Value] | [Value] | [Icon] |
+| [Metric] | [Value] | [Value] | [Icon] |
+
+## Upcoming Work
+
+**Next 2 Weeks**:
+- [Planned work]
+- [Planned work]
+
+**Next Month**:
+- [Milestone or major work]
+
+## Blockers & Risks
+
+### Active Blockers
+- **[Blocker]**: [Description and impact]
+  - Action: [What's being done]
+
+### Risks
+- **[Risk]**: [Description]
+  - Mitigation: [Strategy]
+
+## Discussion Topics
+
+1. [Topic requiring input]
+2. [Topic for alignment]
+
+## Decisions Needed
+
+- [Decision] or None
+
+## Action Items
+
+- [ ] [Action] - @[Owner] - Due: [Date]
+
+## Next Meeting
+
+**Date**: [Date]
+**Focus**: [What next meeting will cover]
+```
+

official-skills/notion-meeting-intelligence/reference/template-selection-guide.md

@@ -0,0 +1,56 @@
+# Meeting Template Selection Guide
+
+Choose the right template for your meeting type.
+
+## Template Overview
+
+| Meeting Type | Use This Template | When to Use |
+|--------------|-------------------|-------------|
+| Make a decision | [Decision Meeting](decision-meeting-template.md) | Need to evaluate options and reach a decision |
+| Project update | [Status Update](status-update-template.md) | Regular check-ins, progress reviews |
+| Generate ideas | [Brainstorming](brainstorming-template.md) | Creative ideation, problem-solving |
+| Sprint planning | [Sprint Planning](sprint-planning-template.md) | Planning agile sprint work |
+| Sprint retro | [Retrospective](retrospective-template.md) | Reflecting on completed work |
+| Manager/report | [1:1 Meeting](one-on-one-template.md) | Regular one-on-one check-ins |
+| Weekly team sync | [Status Update](status-update-template.md) (simplified) | Routine team synchronization |
+
+## Quick Decision Tree
+
+```
+What's the primary purpose?
+
+├─ Make a decision
+│  └─ Use: Decision Meeting Template
+│
+├─ Update on progress
+│  └─ Use: Status Update Template
+│
+├─ Generate ideas
+│  └─ Use: Brainstorming Template
+│
+├─ Plan sprint work
+│  └─ Use: Sprint Planning Template
+│
+├─ Reflect on past work
+│  └─ Use: Retrospective Template
+│
+└─ Manager/report check-in
+   └─ Use: 1:1 Meeting Template
+```
+
+## Template Customization
+
+All templates can be customized:
+- **Simplify** for shorter meetings
+- **Add sections** for specific needs
+- **Combine elements** from multiple templates
+- **Adapt language** for your team culture
+
+## Best Practices
+
+1. **Choose template first**: Select before gathering context
+2. **Gather Notion content**: Search and fetch relevant pages
+3. **Enrich with research**: Add Claude insights where valuable
+4. **Customize as needed**: Adapt template to specific situation
+5. **Share early**: Give attendees time to review
+