@mohanscodex/spectra-code 0.4.9 → 0.5.0

package/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
+

package/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

package/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]
+```
+

package/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]
+```
+