m3tam3re/AGENTS
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Agent restructure

Browse Source
This commit is contained in:
m3tm3re
2026-02-03 20:04:26 +01:00
parent 1f320f1c95
commit 7e4a44eed6
47 changed files with 1 additions and 10709 deletions
Download Patch File Download Diff File Expand all files Collapse all files

69
skills/calendar-scheduling/SKILL.md
View File

@@ -1,69 +0,0 @@
---
name: calendar-scheduling
description: "Calendar and time management with Proton Calendar integration. Use when: (1) checking schedule, (2) blocking focus time, (3) scheduling meetings, (4) time-based planning, (5) managing availability. Triggers: calendar, schedule, when am I free, block time, meeting, availability, what's my day look like."
compatibility: opencode
---
# Calendar & Scheduling
Time management and calendar integration for Proton Calendar.
## Status: Stub
This skill is a placeholder for future development. Core functionality to be added:
## Planned Features
### Schedule Overview
- Daily/weekly calendar view
- Meeting summaries
- Free time identification
### Time Blocking
- Deep work blocks
- Focus time protection
- Buffer time between meetings
### Meeting Management
- Quick meeting creation
- Availability checking
- Meeting prep reminders
### Time-Based Planning
- Energy-matched scheduling
- Context-based time allocation
- Review time protection
## Integration Points
- **Proton Calendar**: Primary calendar backend
- **task-management**: Align tasks with available time
- **ntfy**: Meeting reminders and alerts
## Quick Commands (Future)
| Command | Description |
|---------|-------------|
| `what's my day` | Today's schedule overview |
| `block [duration] for [activity]` | Create focus block |
| `when am I free [day]` | Check availability |
| `schedule meeting [details]` | Create calendar event |
## Proton Calendar Integration
API integration pending. Requires:
- Proton Bridge or API access
- CalDAV sync configuration
- Authentication setup
## Time Blocking Philosophy
Based on Sascha's preferences:
- **Early mornings**: Deep work (protect fiercely)
- **Mid-day**: Meetings and collaboration
- **Late afternoon**: Admin and email
- **Evening**: Review and planning
## Notes
Proton Calendar API access needs to be configured. Consider CalDAV integration or n8n workflow as bridge.

223
skills/chiron-core/SKILL.md
View File

@@ -1,223 +0,0 @@
---
name: chiron-core
description: "Chiron productivity mentor with PARA methodology for Obsidian vaults. Use when: (1) guiding daily/weekly planning workflows, (2) prioritizing work using PARA principles, (3) structuring knowledge organization, (4) providing productivity advice, (5) coordinating between productivity skills. Triggers: chiron, mentor, productivity, para, planning, review, organize, prioritize, focus."
compatibility: opencode
---
# Chiron Core
**Chiron** is the AI productivity mentor - a wise guide named after the centaur who trained Greek heroes. This skill provides the foundational PARA methodology and mentorship persona for the Chiron productivity system.
## Role & Personality
**Mentor, not commander** - Guide the user toward their own insights and decisions.
**Personality traits:**
- Wise but not condescending
- Direct but supportive
- Encourage reflection and self-improvement
- Use Greek mythology references sparingly
- Sign important interactions with 🏛️
## PARA Methodology
The organizing framework for your Obsidian vault at `~/CODEX/`.
### PARA Structure
| Category | Folder | Purpose | Examples |
|----------|---------|---------|----------|
| **Projects** | `01-projects/` | Active outcomes with deadlines | "Website relaunch", "NixOS setup" |
| **Areas** | `02-areas/` | Ongoing responsibilities | "Health", "Finances", "Team" |
| **Resources** | `03-resources/` | Reference material by topic | "Python", "Productivity", "Recipes" |
| **Archive** | `04-archive/` | Completed/inactive items | Old projects, outdated resources |
### Decision Rules
**Use when deciding where to put information:**
1. **Is it actionable with a deadline?** → `01-projects/`
2. **Is it an ongoing responsibility?** → `02-areas/`
3. **Is it reference material?** → `03-resources/`
4. **Is it completed or inactive?** → `04-archive/`
## Workflows
### Morning Planning (/chiron-start)
**When user says**: "Start day", "Morning planning", "What's today?"
**Steps:**
1. Read yesterday's daily note from `daily/YYYY/MM/DD/YYYY-MM-DD.md`
2. Check today's tasks in `tasks/inbox.md` and project files
3. Prioritize using energy levels and deadlines
4. Generate today's focus (3-5 top priorities)
5. Ask: "Ready to start, or need to adjust?"
**Output format:**
```markdown
# 🌅 Morning Plan - YYYY-MM-DD
## Focus Areas
- [Priority 1]
- [Priority 2]
- [Priority 3]
## Quick Wins (<15min)
- [Task]
## Deep Work Blocks
- [Block 1: 9-11am]
- [Block 2: 2-4pm]
## Inbox to Process
- Count items in `00-inbox/`
```
### Evening Reflection (/chiron-end)
**When user says**: "End day", "Evening review", "How was today?"
**Steps:**
1. Review completed tasks
2. Capture key wins and learnings
3. Identify blockers
4. Plan tomorrow's focus
5. Ask for reflection question
**Output format:**
```markdown
# 🌙 Evening Reflection - YYYY-MM-DD
## Wins
- Win 1
- Win 2
- Win 3
## Challenges
- Blocker 1
## Learnings
- Learning 1
## Tomorrow's Focus
- Top 3 priorities
```
### Weekly Review (/chiron-review)
**When user says**: "Weekly review", "Week planning"
**Steps:**
1. Collect completed tasks from daily notes
2. Review project status across all projects
3. Process inbox items
4. Identify patterns and trends
5. Plan next week's priorities
6. Review area health (2-4 weeks review cycle)
**Output format:**
```markdown
# 📊 Weekly Review - W#N
## Metrics
- Tasks completed: N
- Deep work hours: N
- Focus score: N/10
## Top 3 Wins
1. Win 1
2. Win 2
3. Win 3
## Key Learnings
- Learning 1
## Next Week Priorities
1. Priority 1
2. Priority 2
3. Priority 3
## Inbox Status
- Processed N items
- Remaining: N
```
## Task Management
**Use Obsidian Tasks plugin format:**
```markdown
- [ ] Task description #tag ⏫ 📅 YYYY-MM-DD
```
**Priority indicators:**
- ⏫ = Critical (urgent AND important)
- 🔼 = High (important, not urgent)
- 🔽 = Low (nice to have)
**Common tags:**
- `#work` - Work task
- `#personal` - Personal task
- `#quick` - <15 minutes
- `#deep` - Requires focus
- `#waiting` - Blocked/delegated
## File Paths
```
~/CODEX/
├── _chiron/
│ ├── context.md # Primary context (read first)
│ └── templates/ # Note templates
├── 00-inbox/ # Quick captures
├── 01-projects/ # Active projects
├── 02-areas/ # Ongoing responsibilities
├── 03-resources/ # Reference material
├── 04-archive/ # Completed items
├── daily/ # Daily notes
└── tasks/ # Task management
```
## Integration with Other Skills
**chiron-core delegates to:**
- `obsidian-management` - File operations and template usage
- `daily-routines` - Detailed workflow execution
- `task-management` - Task operations
- `quick-capture` - Inbox processing
- `meeting-notes` - Meeting workflows
**Delegation triggers:**
- "Create a project note" → `project-structures` skill
- "Capture this quickly" → `quick-capture` skill
- "Take meeting notes" → `meeting-notes` skill
- "Find all X tasks" → `task-management` skill
## Core Principles
1. **Context first** - Always read `_chiron/context.md` before acting
2. **Minimal friction** - Quick capture should be instant
3. **Trust the system** - Regular reviews keep it useful
4. **Progressive disclosure** - Show what's needed, not everything
5. **Reflect and improve** - Weekly reviews drive system refinement
## When NOT to Use This Skill
- For specific file operations → `obsidian-management`
- For detailed workflow execution → `daily-routines`
- For Basecamp integration → `basecamp`
- For calendar operations → `calendar-scheduling`
- For n8n workflows → `n8n-automation`
## References
- `references/para-guide.md` - Detailed PARA methodology
- `references/priority-matrix.md` - Eisenhower matrix for prioritization
- `references/reflection-questions.md` - Weekly reflection prompts
**Load these references when:**
- User asks about PARA methodology
- Prioritization questions arise
- Weekly review preparation needed
- System improvement suggestions requested

272
skills/chiron-core/references/para-guide.md
View File

@@ -1,272 +0,0 @@
# PARA Methodology Guide
## What is PARA?
PARA is a productivity framework for organizing digital information:
- **P**rojects - Short-term efforts with deadlines
- **A**reas - Long-term responsibilities (no deadline)
- **R**esources - Topics of interest (reference material)
- **A**rchive - Inactive items (completed, cancelled, on hold)
## Why PARA Works
**Traditional problem**: Information scattered across multiple systems with no clear organization.
**PARA solution**: Single organizing principle based on **actionability** and **time horizon**.
## Detailed Definitions
### Projects (01-projects/)
**Definition**: Short-term efforts that you're working on now with clear goals and deadlines.
**Criteria for a project:**
- Has a clear goal or outcome
- Has a deadline or target date
- Takes effort to complete (not a single task)
- Active - you're working on it now
**Examples**:
- "Launch new website" (deadline: March 15)
- "Complete Q1 budget review" (deadline: Feb 28)
- "Learn Python basics" (deadline: End of month)
- "Organize home office" (deadline: This weekend)
**Project structure**:
```
01-projects/[work|personal]/[project-name]/
├── _index.md # Main project file (MOC)
├── meetings/ # Meeting notes
├── decisions/ # Decision records
└── notes/ # General notes
```
**Project frontmatter**:
```yaml
---
status: active | on-hold | completed
deadline: YYYY-MM-DD
priority: critical | high | medium | low
tags: [work, personal]
---
```
### Areas (02-areas/)
**Definition**: Ongoing responsibilities with no end date. These define your roles in life.
**Criteria for an area:**
- No deadline - ongoing indefinitely
- Represents a responsibility or role
- Requires regular attention
- Contains multiple projects over time
**Examples**:
- "Health" (ongoing, has projects: "Run marathon", "Eat better")
- "Finances" (ongoing, has projects: "Tax preparation", "Investment plan")
- "Professional Development" (ongoing, has projects: "Learn AI", "Get certification")
- "Home & Family" (ongoing, has projects: "Plan vacation", "Renovate kitchen")
**Area structure**:
```
02-areas/[work|personal]/
├── health.md
├── finances.md
├── professional-development.md
└── home.md
```
**Area frontmatter**:
```yaml
---
review-frequency: weekly | biweekly | monthly
last_reviewed: YYYY-MM-DD
health: good | needs-attention | critical
---
```
### Resources (03-resources/)
**Definition**: Topics or themes of ongoing interest. Material you reference repeatedly.
**Criteria for a resource:**
- Reference material, not actionable
- Topic-based organization
- Used across multiple projects/areas
- Has long-term value
**Examples**:
- "Python Programming" (referenced for multiple coding projects)
- "Productivity Systems" (used across work and personal)
- "Cooking Recipes" (referenced repeatedly)
- "Productivity Tools" (knowledge about tools)
**Resource structure**:
```
03-resources/
├── programming/
│ ├── python/
│ ├── nix/
│ └── typescript/
├── tools/
│ ├── obsidian.md
│ ├── n8n.md
│ └── nixos.md
├── productivity/
└── cooking/
```
**Resource frontmatter**:
```yaml
---
type: reference | guide | documentation
tags: [programming, tools]
last_updated: YYYY-MM-DD
---
```
### Archive (04-archive/)
**Definition**: Completed or inactive items. Moved here when no longer active.
**When to archive:**
- Projects completed
- Areas no longer relevant (life change)
- Resources outdated
- Items on hold indefinitely
**Archive structure**:
```
04-archive/
├── projects/
├── areas/
└── resources/
```
## Decision Tree
**When deciding where to put something:**
```
Is it actionable?
├─ Yes → Has a deadline?
│ ├─ Yes → PROJECT (01-projects/)
│ └─ No → AREA (02-areas/)
└─ No → Is it reference material?
├─ Yes → RESOURCE (03-resources/)
└─ No → Is it completed/inactive?
├─ Yes → ARCHIVE (04-archive/)
└─ No → Consider if it's relevant at all
```
## PARA in Action
### Example: "Learn Python"
1. **Starts as** Resource in `03-resources/programming/python.md`
- "Interesting topic, want to learn eventually"
2. **Becomes** Area: `02-areas/personal/learning.md`
- "Learning is now an ongoing responsibility"
3. **Creates** Project: `01-projects/personal/learn-python-basics/`
- "Active goal: Learn Python basics by end of month"
4. **Generates** Tasks:
- `tasks/learning.md`:
```markdown
- [ ] Complete Python tutorial #learning ⏫ 📅 2026-02-15
- [ ] Build first project #learning 🔼 📅 2026-02-20
```
5. **Archives** when complete:
- Project moves to `04-archive/projects/`
- Knowledge stays in Resource
## PARA Maintenance
### Weekly Review (Sunday evening)
**Review Projects:**
- Check deadlines and progress
- Mark completed projects
- Identify stalled projects
- Create new projects from areas
**Review Areas:**
- Check area health (all areas getting attention?)
- Identify areas needing projects
- Update area goals
**Review Resources:**
- Organize recent additions
- Archive outdated resources
- Identify gaps
**Process Inbox:**
- File items into appropriate PARA category
- Create projects if needed
- Archive or delete irrelevant items
### Monthly Review (1st of month)
- Review all areas for health
- Identify quarterly goals
- Plan major projects
- Archive old completed items
### Quarterly Review
- Big picture planning
- Area rebalancing
- Life goal alignment
- System optimization
## Common Questions
**Q: Can something be both a Project and a Resource?**
A: Yes, at different times. Example: "Productivity" starts as a Resource (you're interested in it). When you decide to "Implement productivity system," it becomes a Project. After implementation, best practices become a Resource again.
**Q: How do I handle recurring tasks?**
A: If recurring task supports an Area, keep task in Area file and create Project instances when needed:
- Area: "Health" → "Annual physical" (recurring)
- Project: "Schedule 2026 physical" (one-time action with deadline)
**Q: What about someday/maybe items?**
A: Two approaches:
1. Keep in `tasks/someday.md` with low priority (🔽)
2. Archive and retrieve when relevant (PARA encourages active items only)
**Q: Should I organize by work vs personal?**
A: PARA organizes by actionability, not domain. However, within Projects/Areas/Resources, you can create subfolders:
- `01-projects/work/` and `01-projects/personal/`
- `02-areas/work/` and `02-areas/personal/`
## PARA + Obsidian Implementation
**Wiki-links**: Use `[[Project Name]]` for connections
**Tags**: Use `#work`, `#personal`, `#critical` for filtering
**Dataview queries**: Create dashboard views:
```dataview
LIST WHERE status = "active"
FROM "01-projects"
SORT deadline ASC
```
**Templates**: Use `_chiron/templates/` for consistent structure
**Tasks plugin**: Track tasks within PARA structure
## References
- [Forté Labs - PARA Method](https://fortelabs.com/blog/para/)
- [Building a Second Brain](https://buildingasecondbrain.com/)
- Obsidian Tasks Plugin documentation
- Dataview Plugin documentation

347
skills/chiron-core/references/phase1-complete.md
View File

@@ -1,347 +0,0 @@
---
title: "Phase 1 Complete - Work Integration"
type: summary
completed: 2026-01-28
tags: [work, integration, complete]
---
# Phase 1 Complete: Work Integration Foundation
## ✅ Status: Complete
All Phase 1 tasks completed. Work integration foundation is ready to use.
---
## 📦 What Was Delivered
### Skills Created (4 new/updated)
#### 1. Outline Skill (NEW)
**Location**: `skills/outline/SKILL.md`
**Features**:
- Full MCP integration with Vortiago/mcp-outline
- Search wiki documents
- Read/export documents
- Create/update Outline docs
- AI-powered queries (`ask_ai_about_documents`)
- Collection management
- Batch operations
**References**:
- `references/outline-workflows.md` - Detailed usage examples
- `references/export-patterns.md` - Obsidian integration patterns
#### 2. Enhanced Basecamp Skill
**Location**: `skills/basecamp/SKILL.md`
**New Features**:
- Project mapping configuration
- Integration with PARA structure
- Usage patterns for real projects
#### 3. Enhanced Daily Routines Skill
**Location**: `skills/daily-routines/SKILL.md`
**New Features**:
- Morning planning with Basecamp + Outline context
- Evening reflection with work metrics
- Weekly review with project status tracking
- Work area health review
- Work inbox processing
#### 4. Enhanced Meeting Notes Skill
**Location**: `skills/meeting-notes/references/teams-transcript-workflow.md`
**New Features**:
- Teams transcript processing workflow
- Manual DOCX → text → AI analysis → meeting note → Basecamp sync
- Complete templates and troubleshooting guide
### Documentation Created (3)
#### 1. Work PARA Structure Guide
**Location**: `skills/chiron-core/references/work-para-structure.md`
**Content**: Complete PARA organization for work
- Directory tree with projects/areas/resources
- Project mapping to Basecamp
- Integration workflows
- Job transition checklist
- Quick command reference
#### 2. Work Quick Start Guide
**Location**: `skills/chiron-core/references/work-quickstart.md`
**Content**: User-facing quick reference
- First-time setup instructions
- Daily workflow examples
- Tool-specific command patterns
- Integration use cases
- Troubleshooting
#### 3. Teams Transcript Workflow
**Location**: `skills/meeting-notes/references/teams-transcript-workflow.md`
**Content**: Complete manual workflow
- Step-by-step transcript processing
- AI analysis prompts
- Obsidian templates
- Basecamp sync integration
- Automation points for n8n (future)
### PARA Structure Created
#### Work Projects
**Location**: `~/CODEX/01-projects/work/`
**Created**: 10 project folders (placeholders for customization)
Projects:
1. api-integration-platform
2. customer-portal-redesign
3. marketing-campaign-q1
4. security-audit-2026
5. infrastructure-migration
6. mobile-app-v20
7. team-onboarding-program
8. data-analytics-dashboard
9. documentation-revamp
10. api-gateway-upgrade
Each project includes:
- `_index.md` (MOC with Basecamp link)
- `meetings/` directory
- `decisions/` directory
- `notes/` directory
#### Work Areas
**Location**: `~/CODEX/02-areas/work/`
**Created**: 5 area files
Areas:
1. current-job.md - Current employment responsibilities
2. professional-dev.md - Learning and career development
3. team-management.md - Team coordination and leadership
4. company-knowledge.md - Organization context and processes
5. technical-excellence.md - Code quality and standards
#### Work Resources
**Location**: `~/CODEX/03-resources/work/wiki-mirror/`
**Purpose**: Ready for Outline wiki exports
#### Work Archive
**Location**: `~/CODEX/04-archive/work/`
**Purpose**: Ready for completed work and job transitions
---
## 🔄 Integrations Configured
### Basecamp ↔ Obsidian
- Project mapping infrastructure ready
- Morning planning fetches Basecamp todos
- Evening reflection reviews project progress
- Weekly review checks all project status
### Outline ↔ Obsidian
- Search wiki for work context
- Export decisions/docs to vault
- AI-powered knowledge discovery
- Wiki index management
### Teams → Obsidian → Basecamp
- Manual DOCX processing workflow
- AI analysis of transcripts
- Meeting note creation
- Optional action items sync to Basecamp
- Complete documentation and troubleshooting
### All Integrated into Daily/Weekly Routines
- Morning: Basecamp + Outline + personal priorities
- Evening: Work metrics + personal reflection
- Weekly: Project status + area health + planning
---
## 🚀 Ready to Use
### Immediate Workflows
#### Morning Planning with Work
```bash
"/chiron-start"
```
**What happens**:
1. Checks yesterday's completed tasks
2. Fetches today's Basecamp todos
3. Checks Outline for relevant docs
4. Creates integrated morning plan
#### Evening Reflection with Work
```bash
"/chiron-end"
```
**What happens**:
1. Reviews completed Basecamp tasks
2. Reviews project progress
3. Captures work learnings
4. Plans tomorrow's work priorities
#### Weekly Work Review
```bash
"/chiron-review"
```
**What happens**:
1. Checks all Basecamp project status
2. Reviews work area health
3. Identifies at-risk projects
4. Plans next week's priorities
#### Project Status Check
```bash
"What's in [project name]?"
"What's status of API Integration Platform?"
```
**What happens**:
- Fetches from Basecamp
- Shows completion status
- Lists overdue items
- Highlights blockers
#### Wiki Search
```bash
"Search Outline for API authentication"
"Ask Outline: How do we handle rate limiting?"
```
**What happens**:
- Searches Outline wiki
- Returns relevant documents
- AI synthesizes across docs
#### Teams Transcript Processing
```bash
"Process transcript: meeting.docx"
```
**What happens**:
1. Extracts text from DOCX
2. AI analyzes: attendees, topics, decisions, action items
3. Creates meeting note in Obsidian
4. Optionally syncs action items to Basecamp
---
## 📋 Your Next Steps (Optional)
### 1. Customize Projects (Recommended)
The 10 project folders use placeholder names. Customize with your actual Basecamp projects:
```bash
# Option A: Use Basecamp MCP (when ready)
"Show my Basecamp projects"
# → Get actual project names
# → Update project folder names
# → Update _index.md with real project IDs
# Option B: Manual customization
cd ~/CODEX/01-projects/work
# Rename folders to match your actual projects
# Update each _index.md frontmatter:
# - basecamp_id: "project_123"
# - basecamp_url: "https://..."
# - deadline: YYYY-MM-DD
# - status: active/on-hold
```
### 2. Configure Outline MCP
```bash
# Install Outline MCP server
pip install mcp-outline
# Configure in your Opencode/MCP client
# See: https://github.com/Vortiago/mcp-outline
# Set OUTLINE_API_KEY and OUTLINE_API_URL
```
### 3. Test Workflows
Test each integration:
- Morning planning with Basecamp fetch
- Project status check
- Wiki search
- Evening reflection
- Weekly review
### 4. Process First Teams Transcript
Follow the workflow:
```bash
# 1. Download transcript from Teams
# 2. Extract text
python extract_transcript.py meeting.docx
# 3. Ask AI to analyze
# 4. Create meeting note
# 5. Optionally sync action items to Basecamp
```
### 5. Add n8n Automation (When Ready)
When your cloud n8n is ready, add these workflows:
1. **Daily Basecamp → Obsidian sync** - Export new todos/changes
2. **Outline → Obsidian mirror** - Daily export of updated docs
3. **Teams transcript auto-processing** - Watch folder, process automatically
4. **Weekly report generation** - Aggregate work metrics
5. **Mobile task reminders** - Send due tasks to ntfy
---
## 🎯 Key Benefits
### Tool Agnostic
- All work knowledge in Obsidian (your vault)
- Easy to switch jobs: archive work/, update tool configs
- PARA methodology persists regardless of tools
### Real-Time + Persistent
- Basecamp: Real-time task tracking
- Outline: Real-time wiki search
- Obsidian: Persistent knowledge storage
### AI-Powered
- Teams transcripts: AI analysis of meetings
- Wiki: AI-powered semantic search
- Workflows: AI-assisted prioritization
### Complete Integration
- Morning plans include: Basecamp + Outline + personal
- Evening reflections include: Work metrics + personal
- Weekly reviews cover: Projects + areas + inbox
---
## 📊 Commit Details
**Commits**:
- `e2932d1`: Initial Phase 1 implementation (skills + structure)
- `325e06a`: Documentation (quickstart guide)
- `e2932d1` (rebase): Final commit pushed to remote
**Repository**: `code.m3ta.dev:m3tam3re/AGENTS.git`
---
## 🔗 Documentation Links
For detailed guides, see:
- **Work PARA Structure**: `skills/chiron-core/references/work-para-structure.md`
- **Quick Start**: `skills/chiron-core/references/work-quickstart.md`
- **Basecamp Skill**: `skills/basecamp/SKILL.md`
- **Outline Skill**: `skills/outline/SKILL.md`
- **Daily Routines**: `skills/daily-routines/SKILL.md`
- **Meeting Notes**: `skills/meeting-notes/references/teams-transcript-workflow.md`
- **Outline Workflows**: `skills/outline/references/outline-workflows.md`
- **Export Patterns**: `skills/outline/references/export-patterns.md`
---
**Phase 1 Status**: ✅ COMPLETE
**Last Updated**: 2026-01-28

270
skills/chiron-core/references/priority-matrix.md
View File

@@ -1,270 +0,0 @@
# Priority Matrix (Eisenhower)
## The Matrix
Prioritize tasks based on two dimensions:
1. **Urgency** - Time-sensitive
2. **Importance** - Impact on goals
| | **Important** | **Not Important** |
|---|---------------|------------------|
| **Urgent** | ⏫ Critical 🔥 | 🔼 High (Do or Delegate) |
| **Not Urgent** | 🔼 High (Schedule) | 🔽 Low (Eliminate) |
## Quadrant Breakdown
### Quadrant 1: Urgent & Important (⏫ Critical)
**Do immediately. These are crises or deadlines.**
**Characteristics:**
- Time-sensitive
- Has direct impact
- Must be done now
- Often stressful
**Examples:**
- Project due today
- Client emergency
- Health issue
- Financial deadline
**Strategy:**
- Handle now
- Identify root causes (why was it urgent?)
- Prevent recurrence through planning
### Quadrant 2: Not Urgent & Important (🔼 High - Schedule)
**This is where quality happens. These are your priorities.**
**Characteristics:**
- Strategic work
- Long-term goals
- Personal growth
- Relationship building
**Examples:**
- Strategic planning
- Skill development
- Exercise
- Deep work projects
- Relationship time
**Strategy:**
- **Block time** on calendar
- Protect from interruptions
- Schedule first (before urgent items)
- This should be 60-80% of your time
### Quadrant 3: Urgent & Not Important (🔼 High - Do or Delegate)
**These are distractions. Minimize or delegate.**
**Characteristics:**
- Time-sensitive but low impact
- Other people's priorities
- Interruptions
- Some meetings
**Examples:**
- Most email
- Some meetings
- Coworker requests
- Unscheduled calls
- Many notifications
**Strategy:**
- **Delegate** if possible
- Say no more often
- Batch process (check email 2x/day)
- Set expectations about response time
- Aim to minimize this to <20%
### Quadrant 4: Not Urgent & Not Important (🔽 Low - Eliminate)
**These are time-wasters. Remove them.**
**Characteristics:**
- No urgency
- No importance
- Entertainment masquerading as work
- Habits that don't serve you
**Examples:**
- Doom scrolling
- Excessive social media
- Mindless TV
- Busy work that has no impact
- Low-priority tasks you procrastinate on
**Strategy:**
- **Eliminate** ruthlessly
- Set time limits
- Use app blockers if needed
- Replace with value activities
## Task Priority Symbols
Use these symbols in your task format:
```markdown
- [ ] Task description #tag ⏫ 📅 YYYY-MM-DD
```
| Symbol | Meaning | When to use |
|--------|---------|-------------|
| ⏫ | Critical (Q1) | Urgent AND important |
| 🔼 | High (Q2/Q3) | Important but not urgent OR urgent but delegate-able |
| 🔽 | Low (Q4) | Neither urgent nor important |
## Daily Prioritization Workflow
### Morning Plan
1. **List all tasks for today**
2. **Categorize by quadrant**:
```
⏫ Critical (Do Now):
- [Task 1]
- [Task 2]
🔼 High (Schedule):
- [Task 3]
- [Task 4]
🔽 Low (Maybe):
- [Task 5]
```
3. **Limit Critical tasks**: Max 3-4 per day
4. **Schedule High tasks**: Block time on calendar
5. **Eliminate Low tasks**: Remove or move to someday/maybe
### Time Blocking
**Rule of thumb:**
- 60-80% in Quadrant 2 (strategic work)
- 20% in Quadrant 1 (crises)
- <20% in Quadrant 3 (distractions)
- 0% in Quadrant 4 (eliminate)
**Example schedule:**
```
9:00-11:00 Deep work (Q2) - Project X
11:00-11:30 Handle crises (Q1) - Urgent email
11:30-12:30 Deep work (Q2) - Project X
12:30-13:30 Lunch & break
13:30-14:30 Distractions (Q3) - Batch email
14:30-16:30 Deep work (Q2) - Project Y
16:30-17:00 Wrap up (Q1)
```
## Energy-Based Prioritization
Not all critical tasks should be done at the same time. Consider:
| Energy Level | Best Tasks |
|--------------|------------|
| High (morning) | Complex, creative work (Q2) |
| Medium (midday) | Communication, meetings (Q3) |
| Low (evening) | Admin, simple tasks (Q1 easy wins) |
**Morning energy:**
- Complex problem-solving
- Writing
- Creative work
- Strategic thinking
**Midday energy:**
- Meetings
- Email
- Calls
- Collaboration
**Low energy:**
- Admin tasks
- Filing
- Planning
- Review
## Context-Specific Prioritization
Different contexts require different approaches:
**Work context:**
- Prioritize team deadlines
- Consider stakeholder expectations
- Balance strategic vs tactical
**Personal context:**
- Prioritize health and well-being
- Consider relationships
- Balance work-life boundaries
**Emergency context:**
- Quadrant 1 dominates
- Defer Q2 tasks
- Accept disruption to normal flow
## Common Pitfalls
### **Mistreating Urgency for Importance**
**Problem**: Responding to urgent but unimportant items (Q3) first.
**Solution**: Start with Q2 (schedule important work) before checking email/notifications.
### **Overcommitting to Critical (Q1)**
**Problem**: Having 10+ critical tasks creates paralysis and stress.
**Solution**: Limit to 3-4 critical tasks per day. Move rest to Q2 with realistic deadlines.
### **Neglecting Q2**
**Problem**: Always in reactive mode, never proactive.
**Solution**: Schedule 60-80% of time for Q2. Protect these blocks fiercely.
### **Faking Urgency**
**Problem**: Making tasks urgent to avoid doing them (procrastination disguised as crisis).
**Solution**: Question urgency. "Is this truly time-sensitive, or just uncomfortable?"
### **Perfectionism in Q2**
**Problem**: Spending too long on strategic planning, never executing.
**Solution**: Set time limits for planning. Action produces learning.
## Integration with Chiron Workflows
**Morning Plan**: Use matrix to identify 3-5 ⏫ critical tasks and schedule Q2 blocks
**Weekly Review**: Evaluate how much time was spent in each quadrant, adjust for next week
**Daily Review**: Review urgency/importance of remaining tasks
**Project Planning**: Break projects into Q2 tasks, identify potential Q1 crises
## Quick Reference
```
⏫ = Do now (Urgent + Important)
🔼 = Schedule (Important) OR Delegate (Urgent but not important)
🔽 = Eliminate (Neither urgent nor important)
Goal: 60-80% time on 🔼 (Quadrant 2)
Limit ⏫ to 3-4 per day
Minimize 🔼 (Quadrant 3) to <20%
Eliminate 🔽
```
## Resources
- [Eisenhower Matrix on Wikipedia](https://en.wikipedia.org/wiki/Time_management#The_Eisenhower_Method)
- [Atomic Habits - Habits matrix](https://jamesclear.com/habit-tracker)
- Deep Work (Cal Newport) - Protecting Q2 time

288
skills/chiron-core/references/reflection-questions.md
View File

@@ -1,288 +0,0 @@
# Reflection Questions for Weekly Review
Use these questions during weekly reviews to drive insights and improvement.
## Weekly Review Questions
### Metrics & Data
1. **What numbers tell the story?**
- Tasks completed: ___
- Deep work hours: ___
- Meetings attended: ___
- Focus score (1-10): ___
- Energy level (1-10): ___
2. **What do the numbers reveal?**
- Any patterns in productivity?
- When was I most productive?
- What drained my energy?
### Wins & Celebrations
3. **What were my top 3 wins this week?**
- Win 1: ___
- Win 2: ___
- Win 3: ___
4. **What made these wins possible?**
- What worked well?
- What systems/habits helped?
- How can I replicate this?
5. **What am I proud of (not just achievements)?**
- Personal growth
- Character strengths shown
- Values demonstrated
### Challenges & Blockers
6. **What didn't go as planned?**
- What tasks slipped?
- What blocked progress?
- What unexpected challenges arose?
7. **What were the root causes?**
- External factors?
- Personal patterns?
- System failures?
8. **How did I respond to challenges?**
- What did I do well?
- What could I have done differently?
- What did I learn from this?
### Learnings & Insights
9. **What did I learn this week?**
- New skills or knowledge?
- New perspectives or insights?
- Things that don't work?
10. **What surprised me?**
- About my work?
- About myself?
- About my environment?
11. **What patterns am I noticing?**
- Productivity patterns?
- Energy patterns?
- Thought patterns?
- Relationship patterns?
### Areas Review
12. **How are my key areas?**
For each Area (Work, Health, Finances, Relationships, Learning, etc.):
- Health: ___/10 (needs attention/good/excellent)
- Finances: ___/10
- Work: ___/10
- [Other areas...]
13. **Which areas need attention next week?**
- Area 1: Why? What's needed?
- Area 2: Why? What's needed?
### Projects Review
14. **What's the status of my active projects?**
- Project 1: On track / behind / ahead
- Project 2: On track / behind / ahead
- ...
15. **Which projects need adjustment?**
- What needs to change?
- New deadlines?
- Re-prioritization?
16. **Should I start or stop any projects?**
- Start: ___ (why?)
- Stop: ___ (why?)
### Time & Energy
17. **How did I spend my time?**
- Quadrant 1 (crises): ___%
- Quadrant 2 (strategic): ___%
- Quadrant 3 (distractions): ___%
- Quadrant 4 (waste): ___%
18. **What drained my energy?**
- What activities left me exhausted?
- What environments were draining?
- What interactions were tiring?
19. **What energized me?**
- What activities gave me energy?
- What environments felt good?
- What interactions were uplifting?
### Relationships & Collaboration
20. **Who helped me this week?**
- [Name] - How they helped
- [Name] - How they helped
21. **How did I support others?**
- Who did I help?
- What value did I provide?
22. **Any relationship issues to address?**
- Conflicts?
- Miscommunications?
- Appreciation due?
### System & Process Review
23. **How is my PARA system working?**
- Inbox: Clean / Overflowing
- Projects: Organized / Messy
- Resources: Useful / Neglected
- Tasks: Clear / Overwhelming
24. **What needs adjustment in my systems?**
- Capture process?
- Organization?
- Review frequency?
- Tools or workflows?
25. **What new habit should I try?**
- Based on this week's learnings?
### Next Week Planning
26. **What are my top 3 priorities for next week?**
- Priority 1: ___ (why this?)
- Priority 2: ___ (why this?)
- Priority 3: ___ (why this?)
27. **What MUST get done next week?**
- Non-negotiables (deadlines, commitments)
28. **What would make next week amazing?**
- Stretch goals
- Experiments
- Fun activities
### Personal Growth
29. **How did I grow as a person this week?**
- Character development?
- New perspectives?
- Overcoming fears?
30. **What am I grateful for?**
- List 3-5 things
31. **What's one thing I forgive myself for?**
- Mistake?
- Shortcoming?
- Imperfection?
## Monthly Review Questions
Use these in addition to weekly questions on the 1st of each month:
### Big Picture
1. **What was my main focus this month?**
2. **Did I achieve my monthly goals?**
3. **What was my biggest accomplishment?**
4. **What was my biggest challenge?**
5. **How have I changed this month?**
### Goal Progress
6. **How are my annual goals progressing?**
- Goal 1: On track / behind / ahead
- Goal 2: On track / behind / ahead
7. **Do my goals need adjustment?**
- New goals to add?
- Old goals to remove?
- Deadlines to change?
### Life Balance
8. **How balanced is my life right now?**
- Work vs personal
- Health vs neglect
- Giving vs receiving
9. **What area of life needs most attention?**
10. **What am I ignoring that needs attention?**
### System Optimization
11. **What isn't working in my systems?**
12. **What could be automated?**
13. **What could be simplified?**
14. **What new system would help?**
## Quarterly Review Questions
Use these for strategic planning every 3 months:
### Vision & Direction
1. **Am I still on the right path?**
2. **What's changed in my life/situation?**
3. **Are my goals still relevant?**
4. **What's my vision for next quarter?**
### Strategic Goals
5. **What are my 3 strategic priorities for this quarter?**
6. **What projects support these priorities?**
7. **What should I say NO to?**
8. **What opportunities should I pursue?**
### Life Design
9. **Am I designing my life or just reacting to it?**
10. **What would make this quarter exceptional?**
11. **What risks should I take?**
12. **What would happen if I did nothing differently?**
## Using These Questions
### Weekly Review (30-60 min)
**Recommended flow:**
1. Review completed tasks (5 min)
2. Answer Wins questions (10 min)
3. Answer Challenges questions (10 min)
4. Answer Learnings questions (10 min)
5. Review Areas & Projects (10 min)
6. Review Time & Energy (10 min)
7. Plan next week (10 min)
8. Personal growth reflection (5 min)
**Skip questions that don't resonate.** Quality > quantity.
### Monthly Review (60-90 min)
Add monthly questions to weekly review process.
### Quarterly Review (2-3 hours)
Dedicate focused time for strategic thinking. Consider:
- Away from daily environment
- Journaling and reflection
- Visioning exercises
- Deep thinking about life direction
## Tips for Good Reflections
1. **Be honest** - No one else will see this. Truthful answers lead to growth.
2. **Be specific** - "I was tired" → "I was tired because I stayed up late on Tuesday watching videos"
3. **Be kind to yourself** - Self-criticism without self-compassion = paralysis
4. **Focus on systems** - "I failed" → "What system failed? How can I fix it?"
5. **Look for patterns** - One week is data, four weeks is a pattern
6. **Turn insights into action** - Each learning → one concrete change
## Resources
- [The Review System](https://praxis.fortelabs.co/review/)
- [Atomic Habits - Self-reflection](https://jamesclear.com/habit-tracker)
- [Bullet Journal Migration](https://bulletjournal.com/blogs/bullet-journal-news/the-migration)

157
skills/chiron-core/references/work-para-structure.md
View File

@@ -1,157 +0,0 @@
---
title: "Work PARA Structure"
type: index
created: 2026-01-28
---
# Work PARA Structure
## Overview
PARA structure for work-related projects, areas, and resources. Designed for tool-agnostic knowledge management.
## Directory Tree
```
~/CODEX/
├── 01-projects/work/ # Active work projects
│ ├── api-integration-platform/
│ │ ├── _index.md
│ │ ├── meetings/
│ │ ├── decisions/
│ │ └── notes/
│ ├── customer-portal-redesign/
│ │ └── (same structure)
│ ├── marketing-campaign-q1/
│ ├── security-audit-2026/
│ ├── infrastructure-migration/
│ ├── mobile-app-v20/
│ ├── team-onboarding-program/
│ ├── data-analytics-dashboard/
│ ├── documentation-revamp/
│ └── api-gateway-upgrade/
│
├── 02-areas/work/ # Ongoing work responsibilities
│ ├── current-job.md
│ ├── professional-dev.md
│ ├── team-management.md
│ ├── company-knowledge.md
│ └── technical-excellence.md
│
├── 03-resources/work/ # Work reference material
│ └── wiki-mirror/ # Outline wiki exports
│ └── _wiki-index.md
│
└── 04-archive/work/ # Completed work
├── projects/ # Finished projects
└── employment/ # Job transitions
```
## Project Mapping
| Basecamp Project | PARA Path | Type | Status | Deadline |
|----------------|-----------|-------|---------|-----------|
| API Integration Platform | `01-projects/work/api-integration-platform` | Engineering | Active | 2026-03-15 |
| Customer Portal Redesign | `01-projects/work/customer-portal-redesign` | Product/Design | Active | 2026-04-30 |
| Marketing Campaign Q1 | `01-projects/work/marketing-campaign-q1` | Marketing | Active | 2026-02-28 |
| Security Audit 2026 | `01-projects/work/security-audit-2026` | Security | Active | 2026-03-31 |
| Infrastructure Migration | `01-projects/work/infrastructure-migration` | Operations | Active | 2026-06-30 |
| Mobile App v2.0 | `01-projects/work/mobile-app-v20` | Product | On Hold | 2026-05-15 |
| Team Onboarding Program | `01-projects/work/team-onboarding-program` | HR/Operations | Active | 2026-02-15 |
| Data Analytics Dashboard | `01-projects/work/data-analytics-dashboard` | Engineering | Active | 2026-04-15 |
| Documentation Revamp | `01-projects/work/documentation-revamp` | Documentation | Active | 2026-03-30 |
| API Gateway Upgrade | `01-projects/work/api-gateway-upgrade` | Engineering | On Hold | 2026-07-31 |
## Integration Points
### Basecamp Integration
- **Skill**: `basecamp` (MCP)
- **Mapping**: See Basecamp project IDs → PARA paths
- **Sync**: Manual sync via skill or future n8n automation
- **Status Check**: "What's in [project]?" → Basecamp
### Outline Wiki Integration
- **Skill**: `outline` (MCP)
- **Live Search**: "Search Outline for [topic]"
- **Export**: "Export [document] to Obsidian"
- **Location**: `03-resources/work/wiki-mirror/`
### Teams Meeting Integration
- **Skill**: `meeting-notes`
- **Workflow**: DOCX → AI analysis → meeting note → Basecamp sync
- **Location**: `01-projects/work/[project]/meetings/`
- **Guide**: See `skills/meeting-notes/references/teams-transcript-workflow.md`
## Workflows
### Morning Planning with Work Context
```
1. Read yesterday's daily note
2. Check Basecamp: "Show my Basecamp todos due today"
3. Check Outline: "Search Outline for [project topic]"
4. Create integrated morning plan with:
- Work priorities (from Basecamp)
- Personal priorities (from PARA)
- Meeting schedule
- Deep work blocks
```
### Evening Reflection with Work Context
```
1. Review completed Basecamp tasks
2. Review project progress
3. Capture work learnings
4. Export decisions to Outline (if applicable)
5. Plan tomorrow's work priorities
```
### Weekly Review with Work
```
1. Check all Basecamp project status
2. Review work area health
3. Identify at-risk projects
4. Plan next week's priorities
5. Process work inbox
```
## Job Transition Checklist
When switching jobs:
1. **Archive Current Work**:
- Move `01-projects/work/` → `04-archive/work/[old-company]/`
- Move `02-areas/work/` → `04-archive/work/[old-company]/`
- Keep `03-resources/work/wiki-mirror/` (company knowledge)
2. **Update Tool Configurations**:
- Basecamp: Remove old projects, add new ones
- Outline: Update collections (if switching wikis)
- Keep work structure intact
3. **Create New Work Structure**:
- Create new `01-projects/work/` folders
- Update `02-areas/work/` areas
- Preserve PARA methodology
## Quick Commands
| Action | Command |
|--------|----------|
| Start work day | "/chiron-start" → morning planning with Basecamp |
| End work day | "/chiron-end" → reflection with work metrics |
| Weekly review | "/chiron-review" → work project status review |
| Check Basecamp | "Show my Basecamp projects" or "What's in [project]?" |
| Search wiki | "Search Outline for [topic]" |
| Process meeting | "Process transcript: [file.docx]" |
| Project status | "What's status of [project name]?" |
## Notes
- All work knowledge stored in Obsidian (tool-agnostic)
- Basecamp used for real-time task tracking
- Outline used for live wiki access
- Teams transcripts processed with AI analysis
- n8n automation ready for future implementation
---
**Last updated**: 2026-01-28

374
skills/chiron-core/references/work-quickstart.md
View File

@@ -1,374 +0,0 @@
# Work Integration Quick Start Guide
Quick reference for using your work integration with Basecamp, Outline, and Teams.
## 🚀 First-Time Setup
### 1. Customize Your Projects
The 10 projects in `01-projects/work/` are placeholders. Customize them:
```bash
# Option A: Fetch from Basecamp (when MCP is ready)
"Show my Basecamp projects" → Get actual project names
# Option B: Manual customization
cd ~/CODEX/01-projects/work
# Rename folders to match your actual Basecamp projects
# Update each _index.md with:
# - Correct project name
# - Actual Basecamp project ID
# - Real deadline
# - Actual status
```
### 2. Set Up Outline MCP
```bash
# Install Outline MCP server
pip install mcp-outline
# Configure in your Opencode/MCP client
# See: https://github.com/Vortiago/mcp-outline
# Set OUTLINE_API_KEY and OUTLINE_API_URL
```
### 3. Test Basecamp Connection
```bash
# Test Basecamp MCP
"Show my Basecamp projects"
# Should list your actual projects
# If successful, ready to use
```
---
## 📅 Daily Work Workflow
### Morning Planning
```
"Start day" or "/chiron-start"
```
**What happens**:
1. Checks yesterday's completed tasks
2. Fetches today's Basecamp todos
3. Searches Outline for relevant wiki docs
4. Creates integrated morning plan
**Output includes**:
- Work priorities (from Basecamp)
- Personal priorities (from PARA areas)
- Meeting schedule
- Deep work blocks protected
### During Work Day
**Check Basecamp status**:
```bash
"What's in API Integration Platform?"
"Show my Basecamp todos due today"
"Search Basecamp for OAuth2"
```
**Search wiki for context**:
```bash
"Search Outline for authentication best practices"
"Search Outline for API rate limiting"
```
**Quick capture**:
```bash
"Capture: OAuth2 needs refresh token logic"
# → Saved to 00-inbox/work/
```
**Process meeting transcript**:
```bash
"Process transcript: api-design-review.docx"
# → Creates meeting note
# → Extracts action items
# → Optionally syncs to Basecamp
```
### Evening Reflection
```
"End day" or "/chiron-end"
```
**What happens**:
1. Reviews completed Basecamp tasks
2. Captures work wins and learnings
3. Checks project progress
4. Plans tomorrow's work priorities
5. Updates work metrics
---
## 📊 Weekly Work Review
```
"Weekly review" or "/chiron-review"
```
**What happens**:
1. Checks all Basecamp project status (completion %, overdue items)
2. Reviews work area health
3. Identifies at-risk projects
4. Plans next week's work priorities
5. Processes work inbox
**Output includes**:
- Work metrics (tasks completed, projects progressed)
- Work wins and challenges
- Project status overview (on track, behind, at risk)
- Work area health review
- Next week's priorities
---
## 🔧 Tool-Specific Commands
### Basecamp (Project Management)
**List all projects**:
```bash
"Show my Basecamp projects"
```
**Check project status**:
```bash
"What's in API Integration Platform?"
"What's status of Customer Portal Redesign?"
```
**Create todos**:
```bash
"Add todos to API Integration Platform"
# → Prompts for: project, todo list, tasks with due dates
```
**Search content**:
```bash
"Search Basecamp for OAuth2"
```
### Outline (Wiki Knowledge)
**Search wiki**:
```bash
"Search Outline for API authentication"
"Ask Outline: How do we handle rate limiting?"
```
**Read document**:
```bash
"Show me OAuth2 Setup Guide"
```
**Export to Obsidian**:
```bash
"Export OAuth2 Setup Guide to Obsidian"
# → Saves to 03-resources/work/wiki-mirror/
# → Adds frontmatter with outline source
# → Links to related projects/areas
```
**Create wiki document**:
```bash
"Create Outline doc: API Authentication Decision"
# → Creates in Outline with provided content
# → Adds to appropriate collection
```
### Teams (Meetings)
**Process transcript**:
```bash
"Process transcript: [filename.docx]"
```
**Workflow**:
1. Upload transcript file
2. Extract text from DOCX
3. AI analysis extracts: attendees, topics, decisions, action items
4. Creates meeting note in Obsidian
5. Optionally syncs action items to Basecamp
**Manual steps** (see `skills/meeting-notes/references/teams-transcript-workflow.md`):
```bash
# Step 1: Download transcript from Teams
# Step 2: Extract text
python extract_transcript.py transcript.docx
# Step 3: Ask AI to analyze
# (Paste transcript into AI prompt from workflow guide)
# Step 4: Create meeting note using meeting-notes skill
# Step 5 (Optional): Sync action items to Basecamp
```
---
## 🎯 Quick Reference
| I Want To... | Command | Tool |
|----------------|----------|-------|
| See today's work | "/chiron-start" | Morning planning |
| Review my day | "/chiron-end" | Evening reflection |
| See project status | "What's in [project]?" | Basecamp |
| Find wiki info | "Search Outline for [topic]" | Outline |
| Process meeting | "Process transcript: [file]" | Teams + AI |
| Weekly review | "/chiron-review" | Weekly review |
| Create wiki doc | "Create Outline doc: [title]" | Outline |
| Export wiki doc | "Export [doc] to Obsidian" | Outline |
| Quick capture | "Capture: [thought]" | Quick capture |
---
## 🔗 Integration Examples
### Example 1: Starting a New Project
```bash
# 1. Create project in PARA (manually or from plan-writing)
# 2. Create project folder in 01-projects/work/
# 3. Link to Basecamp (if project exists there)
User: "What's the status of API Integration Platform in Basecamp?"
→ Gets: 65% complete, next milestone: OAuth2 endpoints
User: "Search Outline for OAuth2 setup guides"
→ Gets: 3 relevant documents
User: "Export OAuth2 Setup Guide to Obsidian"
→ Saves to project/notes/oauth2-setup-guide.md
→ Links from project MOC
```
### Example 2: Processing a Meeting
```bash
User: "Process transcript: api-design-review.docx"
System:
1. Extracts text from DOCX
2. AI analyzes: attendees, topics, decisions, action items
3. Creates meeting note: 01-projects/work/api-integration-platform/meetings/api-design-review-20260128.md
4. Outputs action items:
- [ ] Create OAuth2 implementation guide #meeting #todo 🔼 👤 @alice 📅 2026-02-05
- [ ] Document rate limiting policy #meeting #todo 🔼 👤 @bob 📅 2026-02-10
User: "Sync action items to Basecamp?"
→ System creates 2 todos in API Integration Platform project
→ Assigns to Alice and Bob
→ Sets due dates
```
### Example 3: Daily Work Flow
```bash
Morning:
"/chiron-start"
→ Gets: 5 Basecamp todos due today
→ Gets: 2 meetings scheduled
→ Searches Outline: "API authentication patterns"
→ Creates integrated plan:
- Work: Complete OAuth2 flow (P0)
- Work: Review dashboard mockups (P1)
- Meeting: Architecture review (2pm)
- Deep work: 9-11am (OAuth2)
During work:
"Search Basecamp for OAuth2"
→ Finds: 3 docs, 2 todos
Evening:
"/chiron-end"
→ Reviews: OAuth2 flow complete
→ Captures: Learning about token refresh pattern
→ Checks project: 70% complete now
→ Plans: Tomorrow: Finish API endpoints
```
---
## 💡 Best Practices
### Daily Use
1. **Start with morning plan** - Sets focus for the day
2. **Check Basecamp first** - Prioritize work tasks
3. **Search Outline for context** - Get knowledge before starting
4. **Quick capture interruptions** - Don't break flow, capture and continue
5. **End with evening reflection** - Review and plan tomorrow
### Weekly Use
1. **Dedicated time** - 60-90 minutes for weekly review
2. **Check all projects** - Don't forget any
3. **Review area health** - Balance attention across responsibilities
4. **Process inbox** - Keep 00-inbox/ clean
5. **Plan next week** - Set priorities, don't just review
### Tool Use
1. **Basecamp for tasks** - Live task tracking
2. **Outline for knowledge** - Persistent wiki access
3. **Obsidian for storage** - Tool-agnostic knowledge
4. **Teams transcripts** - Process within 24 hours
5. **AI for analysis** - Extract insights from transcripts/docs
---
## 🔧 Troubleshooting
### Basecamp MCP Not Working
**Check**:
- MCP server running?
- API key configured?
- Connection to Basecamp?
### Outline MCP Not Working
**Check**:
- `pip install mcp-outline` completed?
- OUTLINE_API_KEY set?
- OUTLINE_API_URL correct?
### Project Not Found in Basecamp
**Check**:
- Project name matches exactly?
- Project in correct workspace?
### Wiki Search No Results
**Try**:
- Broader query (fewer keywords)
- Remove collection_id to search everywhere
- Use `ask_ai_about_documents` for semantic search
### Transcript Processing Fails
**Check**:
- DOCX file valid?
- `python-docx` installed?
- AI prompt clear enough?
---
## 📚 Documentation Links
For detailed guides, see:
- **PARA Work Structure**: `skills/chiron-core/references/work-para-structure.md`
- **Basecamp Skill**: `skills/basecamp/SKILL.md`
- **Outline Skill**: `skills/outline/SKILL.md`
- **Daily Routines**: `skills/daily-routines/SKILL.md`
- **Meeting Notes**: `skills/meeting-notes/SKILL.md`
- **Teams Transcript Workflow**: `skills/meeting-notes/references/teams-transcript-workflow.md`
- **Outline Workflows**: `skills/outline/references/outline-workflows.md`
- **Export Patterns**: `skills/outline/references/export-patterns.md`
---
**Last updated**: 2026-01-28

78
skills/communications/SKILL.md
View File

@@ -1,78 +0,0 @@
---
name: communications
description: "Email and communication management with Proton Mail integration. Use when: (1) drafting emails, (2) managing follow-ups, (3) communication tracking, (4) message templates, (5) inbox management. Triggers: email, draft, reply, follow up, message, inbox, communication, respond to."
compatibility: opencode
---
# Communications
Email and communication management for Proton Mail.
## Status: Stub
This skill is a placeholder for future development. Core functionality to be added:
## Planned Features
### Email Drafting
- Context-aware draft generation
- Tone matching (formal/casual)
- Template-based responses
### Follow-up Tracking
- Waiting-for list management
- Follow-up reminders
- Response tracking
### Inbox Management
- Priority sorting
- Quick triage assistance
- Archive recommendations
### Communication Templates
- Common response patterns
- Meeting request templates
- Status update formats
## Integration Points
- **Proton Mail**: Primary email backend
- **task-management**: Convert emails to tasks
- **ntfy**: Important email alerts
- **n8n**: Automation workflows
## Quick Commands (Future)
| Command | Description |
|---------|-------------|
| `draft reply to [context]` | Generate email draft |
| `follow up on [topic]` | Check follow-up status |
| `email template [type]` | Use saved template |
| `inbox summary` | Overview of pending emails |
## Proton Mail Integration
API integration pending. Options:
- Proton Bridge (local IMAP/SMTP)
- n8n with email triggers
- Manual copy/paste workflow initially
## Communication Style Guide
Based on Sascha's profile:
- **Tone**: Professional but approachable
- **Length**: Concise, get to the point
- **Structure**: Clear ask/action at the top
- **Follow-up**: Set clear expectations
## Email Templates (Future)
- Meeting request
- Status update
- Delegation request
- Follow-up reminder
- Thank you / acknowledgment
## Notes
Start with manual draft assistance. Proton Mail API integration can be added via n8n workflow when ready.

675
skills/daily-routines/SKILL.md
View File

@@ -1,675 +0,0 @@
---
name: daily-routines
description: "Daily and weekly productivity workflows for Chiron system. Use when: (1) morning planning, (2) evening reflection, (3) weekly review, (4) prioritizing work, (5) reviewing progress. Triggers: morning, evening, weekly, review, planning, start day, end day, prioritize."
compatibility: opencode
---
# Daily Routines
Morning planning, evening reflection, and weekly review workflows for the Chiron productivity system.
## Workflows
### Morning Plan (/chiron-start)
**When user says**: "Start day", "Morning planning", "What's today?", "/chiron-start"
**Steps:**
1. **Read yesterday's daily note**
- File: `~/CODEX/daily/YYYY/MM/DD/YYYY-MM-DD.md`
- Extract: incomplete tasks, carry-over items
2. **Check today's tasks**
- Read `~/CODEX/tasks/inbox.md`
- Scan project files for today's tasks
- Check calendar (via calendar-scheduling skill)
3. **Prioritize using energy and deadlines**
- High energy: Complex, creative work (Quadrant 2)
- Medium energy: Communication, collaboration (Quadrant 3)
- Low energy: Admin, simple tasks (Quadrant 1 easy wins)
4. **Create today's plan**
- 3-5 critical tasks (⏫)
- 5-8 high priority tasks (🔼)
- Schedule deep work blocks
- Identify quick wins
5. **Generate daily note using template**
- Template: `_chiron/templates/daily-note.md`
- Fill: focus areas, energy blocks, tasks
6. **Ask for confirmation**
- "Ready to start, or need to adjust?"
**Output format:**
```markdown
# 🌅 Morning Plan - YYYY-MM-DD
## Focus Areas (Top 3)
1. [Priority 1] - [estimated time]
2. [Priority 2] - [estimated time]
3. [Priority 3] - [estimated time]
## Deep Work Blocks
- [9:00-11:00] [Project A]
- [14:00-16:00] [Project B]
## Quick Wins (<15min)
- [Task 1]
- [Task 2]
- [Task 3]
## Meetings
- [10:00-11:00] [Meeting title]
## Carried Over from Yesterday
- [Task from yesterday]
## Inbox to Process
- [X] items in 00-inbox/ to process
```
**Delegation triggers:**
- Calendar operations → `calendar-scheduling`
- Task extraction → `task-management`
- File operations → `obsidian-management`
### Evening Reflection (/chiron-end)
**When user says**: "End day", "Evening review", "How was today?", "/chiron-end"
**Steps:**
1. **Review completed tasks**
- Check off completed items in daily note
- Count completed vs planned
- Identify wins
2. **Capture key learnings**
- What went well?
- What didn't?
- What surprised me?
3. **Identify blockers**
- What stopped progress?
- What resources were missing?
- What context was challenging?
4. **Update daily note**
- Mark completed tasks
- Add wins section
- Add challenges section
- Add learnings section
5. **Plan tomorrow**
- Carry over incomplete tasks
- Identify tomorrow's priorities
- Note energy levels
6. **Ask reflection question**
- Example: "What's one thing you're grateful for today?"
**Output format:**
```markdown
# 🌙 Evening Reflection - YYYY-MM-DD
## Tasks Completed
- ✅ [Task 1]
- ✅ [Task 2]
- ⏭️ [Task 3 - carried over]
## Wins
1. [Win 1] - why this matters
2. [Win 2] - why this matters
3. [Win 3] - why this matters
## Challenges
- [Blocker 1] - impact and next step
- [Blocker 2] - impact and next step
## Learnings
- [Learning 1]
- [Learning 2]
## Tomorrow's Focus
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]
## Energy Level
- Morning: ___/10
- Midday: ___/10
- Evening: ___/10
## Reflection
[User's response to reflection question]
```
**Delegation triggers:**
- Task updates → `task-management`
- Note updates → `obsidian-management`
### Weekly Review (/chiron-review)
**When user says**: "Weekly review", "Week planning", "/chiron-review"
**Steps:**
1. **Collect daily notes for the week**
- Read all daily notes from Monday-Sunday
- Extract: completed tasks, wins, challenges
2. **Calculate metrics**
- Tasks completed count
- Deep work hours (estimate from daily notes)
- Focus score (self-rated from daily notes)
- Quadrant distribution (time spent)
3. **Review project status**
- Scan all projects in `01-projects/`
- Check: status, deadlines, progress
- Identify: stalled projects, completed projects, new projects needed
4. **Process inbox**
- Review items in `00-inbox/`
- File to appropriate PARA category
- Delete irrelevant items
- Create tasks from actionable items
5. **Review area health**
- Check `02-areas/` files
- Identify areas needing attention
- Update area status (health scores)
6. **Identify patterns and trends**
- Productivity patterns
- Energy patterns
- Recurring blockers
7. **Plan next week**
- Top 3 priorities
- Key projects to focus on
- Areas to nurture
- New habits to try
8. **Generate weekly review note**
- Template: `_chiron/templates/weekly-review.md`
- File: `~/CODEX/daily/weekly-reviews/YYYY-W##.md`
**Output format:**
```markdown
# 📊 Weekly Review - W## (Mon DD-MMM to Sun DD-MMM)
## Metrics
- Tasks completed: NN
- Deep work hours: NN
- Focus score average: N.N/10
- Energy score average: N.N/10
- Quadrant distribution: Q1: NN%, Q2: NN%, Q3: NN%, Q4: NN%
## Top 3 Wins
1. [Win 1] - impact and why it mattered
2. [Win 2] - impact and why it mattered
3. [Win 3] - impact and why it mattered
## Key Challenges
- [Challenge 1] - root cause and solution
- [Challenge 2] - root cause and solution
## Patterns & Insights
- Productivity pattern: [observation]
- Energy pattern: [observation]
- Recurring blocker: [observation]
## Project Status
### Completed
- [Project 1] - outcome
- [Project 2] - outcome
### On Track
- [Project 1] - progress, deadline
- [Project 2] - progress, deadline
### Behind Schedule
- [Project 1] - why, what's needed
### New Projects Started
- [Project 1] - goals, deadline
- [Project 2] - goals, deadline
### Stalled Projects
- [Project 1] - why stalled, action needed
## Area Health Review
| Area | Health | Needs Attention |
|-------|--------|----------------|
| Health | N/10 | [specific needs] |
| Finances | N/10 | [specific needs] |
| Work | N/10 | [specific needs] |
| Relationships | N/10 | [specific needs] |
| Learning | N/10 | [specific needs] |
## Inbox Status
- Items processed: NN
- Items remaining: NN
- Filed to Projects: NN
- Filed to Resources: NN
- Archived: NN
- Deleted: NN
## Next Week Priorities
### Top 3
1. [Priority 1] - why critical
2. [Priority 2] - why important
3. [Priority 3] - why important
### Projects to Focus
- [Project 1] - key milestone
- [Project 2] - key milestone
- [Project 3] - key milestone
### Areas to Nurture
- [Area 1] - specific focus
- [Area 2] - specific focus
### New Habits/Experiments
- [Habit 1] - what to try
- [Habit 2] - what to try
## Reflection Question
[Weekly reflection from chiron-core references/reflection-questions.md]
```
**Delegation triggers:**
- PARA organization → `chiron-core`
- Task aggregation → `task-management`
- File operations → `obsidian-management`
- Area review → `chiron-core`
## Integration with Other Skills
**Calls to:**
- `obsidian-management` - Create/update daily notes, templates
- `task-management` - Extract/update tasks
- `chiron-core` - PARA guidance, prioritization, reflection questions
- `calendar-scheduling` - Calendar integration
- `basecamp` - Fetch work todos, check project status
- `outline` - Search wiki for work context
**Delegation rules:**
- User wants to understand PARA → `chiron-core`
- User asks about tasks → `task-management`
- User needs file operations → `obsidian-management`
- User needs calendar → `calendar-scheduling`
- User needs work context → `basecamp`
- User needs wiki knowledge → `outline`
---
## Work Context Integration
### Morning Planning with Work
**Enhanced morning plan workflow:**
```
1. Read yesterday's daily note (personal + work)
2. Check today's work todos:
- Delegate to basecamp skill: "Show my Basecamp todos due today"
- Get: project name, task title, due date, assignee
3. Check project status:
- For each active work project:
Delegate to basecamp: "What's status of [project]?"
- Get: completion %, overdue items, next milestones
4. Check wiki for relevant docs:
- Delegate to outline: "Search Outline for [topic]"
- Get: related docs, decisions, processes
5. Create integrated morning plan:
- Personal priorities (from PARA areas)
- Work priorities (from Basecamp)
- Meeting schedule (from calendar)
- Deep work blocks aligned with energy
```
**Morning plan with work context:**
```markdown
# 🌅 Morning Plan - YYYY-MM-DD
## Work Focus (Top 3)
1. [[API Integration Platform]] - Complete OAuth flow (Basecamp: 3 todos today)
2. [[Customer Portal Redesign]] - Review mockups (Basecamp: 2 todos due)
3. [[Data Analytics Dashboard]] - Fix query performance (Basecamp: 1 overdue)
## Personal Focus (Top 2)
1. Health - Morning workout
2. Finances - Review monthly budget
## Deep Work Blocks
- [9:00-11:00] [[API Integration Platform]] (High energy, no meetings)
- [14:00-16:00] [[Customer Portal Redesign]] (Design work)
## Meetings (Work)
- [11:00-12:00] Project Sync (Teams)
- [15:00-16:00] Architecture Review (Zoom)
## Quick Wins (<15min)
- [ ] Respond to urgent emails
- [ ] Update project status in Basecamp
- [ ] Process inbox items (3 items)
## Work Wiki Resources
- 📄 [[OAuth Setup Guide]](outline://doc/abc123) - Reference for project 1
- 📄 [[UI Design System]](outline://doc/def456) - Reference for project 2
## Inbox to Process
- [X] items in 00-inbox/ to process
```
### Evening Reflection with Work
**Enhanced evening reflection workflow:**
```
1. Review completed tasks (personal + work)
- Check Basecamp: "What did I complete today in Basecamp?"
- Get: todos marked complete, cards moved to Done
2. Check project progress:
- For each active project: get status
- Note: milestones reached, blockers encountered
3. Capture work learnings:
- Technical learnings (to document later)
- Process insights (to export to wiki)
- Team collaboration notes
4. Sync to Obsidian:
- Create work summary in project notes
- Export decisions to Outline (if n8n available)
5. Plan tomorrow:
- Carry over incomplete Basecamp todos
- Update project priorities based on today's progress
- Identify personal priorities
```
**Evening reflection with work context:**
```markdown
# 🌙 Evening Reflection - YYYY-MM-DD
## Work Tasks Completed
- ✅ Complete OAuth2 implementation (Basecamp)
- ✅ Review dashboard mockups (Basecamp)
- ✅ Respond to 5 team messages (Teams)
- ⏭️ Fix query performance (carried over)
## Personal Tasks Completed
- ✅ Morning workout
- ✅ Weekly grocery shopping
- ⏭️ Read book chapter (carried over)
## Work Wins
1. OAuth2 implementation complete ahead of schedule
2. Team approved dashboard design direction
3. Documented architecture decision in wiki
## Personal Wins
1. Maintained morning routine
2. Saved money on groceries
## Work Challenges
- Blocker: Waiting for API key from security team (project 1)
- Solution: Scheduled meeting tomorrow to expedite
## Work Learnings
- OAuth2 token refresh pattern is simpler than expected
- Team prefers async communication over meetings
## Project Status Updates
### [[API Integration Platform]]
- Progress: 65% complete
- Completed: OAuth2, token management
- Next: API endpoints implementation
- Deadline: 2026-03-15 (on track)
### [[Customer Portal Redesign]]
- Progress: 40% complete
- Completed: Research, mockups
- Next: User testing
- Deadline: 2026-04-30 (slightly behind)
## Tomorrow's Work Focus
1. Complete API endpoints (OAuth Integration Platform)
2. Conduct user testing (Customer Portal Redesign)
3. Follow up on API key (Security team)
## Tomorrow's Personal Focus
1. Evening workout
2. Update budget with new expenses
## Energy Level
- Morning: 8/10
- Midday: 6/10 (meeting-heavy)
- Evening: 7/10
## Reflection
[User's response]
```
### Weekly Review with Work
**Enhanced weekly review workflow:**
```
1. Collect completed work:
- Get Basecamp stats: "Show my completed todos this week"
- Get project milestones achieved
2. Review all projects:
- For each work project: get status
- Identify: at risk, on track, completed
3. Review area health:
- Work areas: current-job, team-management, technical-excellence
- Check: balance, attention needed
4. Process work inbox:
- Review 00-inbox/work/ items
- File to appropriate work projects or areas
5. Plan next week:
- Work priorities from Basecamp
- Project milestones to focus on
- Personal priorities from PARA areas
```
**Weekly review with work context:**
```markdown
# 📊 Weekly Review - W## (Mon DD-MMM to Sun DD-MMM)
## Work Metrics
- Basecamp tasks completed: 23
- Projects progressed: 5
- Meetings attended: 12
- Documents created/updated: 8
- Wiki exports: 3 decisions, 2 guides
## Personal Metrics
- Tasks completed: 15
- Deep work hours: 8
- Focus score: 7.5/10
## Work Wins
1. OAuth2 platform delivered 3 days early
2. Team approved new architecture decision
3. Security audit passed with minor findings
## Personal Wins
1. Maintained workout routine (5/5 days)
2. Read 2 books
3. Saved target amount
## Work Challenges
- Challenge 1: API integration delayed by dependency
Root cause: Waiting on security team approval
Solution: Parallel track started for next sprint
## Work Patterns
- Productivity: High on Mon-Tue, dropped on Fri (meeting-heavy)
- Energy: Mornings best for deep work, afternoons for collaboration
- Meetings: Average 2.4/day, need to reduce to 1-2
## Project Status
### Completed
- [[Security Audit 2026]] - Passed with 2 minor findings
### On Track
- [[API Integration Platform]] - 65% complete, on track
- [[Customer Portal Redesign]] - 40% complete, slightly behind
- [[Data Analytics Dashboard]] - 70% complete, ahead of schedule
### Behind Schedule
- [[Documentation Revamp]] - Delayed waiting for SME availability
Action: Book dedicated session next week
### At Risk
- [[Infrastructure Migration]] - Waiting on approval from ops team
Action: Escalate to manager tomorrow
### Stalled
- [[Mobile App v2.0]] - On hold, waiting for strategy decision
Action: Follow up with product owner
## Work Area Health Review
| Area | Health | Needs Attention |
|-------|--------|----------------|
| Current Job | 8/10 | Balance work/personal time better |
| Professional Dev | 9/10 | On track with learning goals |
| Team Management | 7/10 | Follow up on stalled mobile app |
| Company Knowledge | 6/10 | Need to document more processes |
| Technical Excellence | 8/10 | Good code quality, maintain standards |
## Work Inbox Status
- Items processed: 12
- Items remaining: 3
- Filed to Projects: 8
- Filed to Resources: 2
- Archived: 1
## Next Week Work Priorities
### Top 3
1. Complete API endpoints (API Integration Platform) - Critical path
2. User testing feedback (Customer Portal Redesign) - Milestone due
3. Follow up on infrastructure approval (Infrastructure Migration) - Unblock project
### Projects to Focus
- [[API Integration Platform]] - Deliver MVP
- [[Customer Portal Redesign]] - User testing phase
- [[Data Analytics Dashboard]] - Performance optimization
### Work Areas to Nurture
- Team Management - Address mobile app stall
- Company Knowledge - Document 3 key processes
- Technical Excellence - Code review for new OAuth implementation
## Next Week Personal Priorities
### Top 3
1. Health - 5 workouts, meal prep
2. Finances - Monthly review, budget adjustment
3. Learning - Complete TypeScript course module
## Work Habits/Experiments
- Try: 2-hour deep work blocks (instead of 1.5 hours)
- Try: No meeting mornings (9-11 AM protected)
- Try: End-of-day 15-min Basecamp review
## Reflection Question
[Weekly reflection from chiron-core references/reflection-questions.md]
```
## Workflow Decision Tree
```
User request
│
├─ "Start day" → Morning Plan
│ ├─ Read yesterday's note
│ ├─ Check today's tasks
│ ├─ Prioritize (delegate to chiron-core)
│ ├─ Create daily note (delegate to obsidian-management)
│ └─ Confirm focus
│
├─ "End day" → Evening Reflection
│ ├─ Review completed tasks
│ ├─ Capture wins/challenges
│ ├─ Update daily note (delegate to obsidian-management)
│ ├─ Plan tomorrow
│ └─ Ask reflection question
│
└─ "Weekly review" → Weekly Review
├─ Collect daily notes
├─ Calculate metrics
├─ Review projects
├─ Process inbox (delegate to quick-capture)
├─ Review areas (delegate to chiron-core)
├─ Identify patterns
├─ Plan next week
└─ Generate review note (delegate to obsidian-management)
```
## Templates
All workflows use templates from `_chiron/templates/`:
| Workflow | Template | Variables |
|----------|----------|------------|
| Morning Plan | `daily-note.md` | {{date}}, {{focus}}, {{tasks}} |
| Evening Reflection | `daily-note.md` (update) | N/A |
| Weekly Review | `weekly-review.md` | {{week}}, {{date}}, {{metrics}} |
**Template usage:**
1. Read template file
2. Replace variables with actual data
3. Create/update note in appropriate location
4. Fill in placeholder sections
## Best Practices
### Morning Planning
- Limit critical tasks to 3-5
- Schedule deep work blocks first
- Protect high-energy times
- Include breaks and transition time
### Evening Reflection
- Focus on patterns, not just details
- Be honest about challenges
- Capture learnings, not just outcomes
- Plan tomorrow before bed
### Weekly Review
- Dedicated time (60-90 min)
- Use reflection questions from chiron-core
- Focus on system improvements
- Plan, don't just review
## Quick Reference
| Workflow | Trigger | Duration | Output |
|----------|----------|-----------|--------|
| Morning Plan | "Start day", "/chiron-start" | 5-10 min | Daily note with focus areas |
| Evening Reflection | "End day", "/chiron-end" | 5-10 min | Updated daily note |
| Weekly Review | "Weekly review", "/chiron-review" | 60-90 min | Weekly review note |
## Resources
- `references/reflection-questions.md` - Weekly and monthly reflection questions (from chiron-core)
- `references/weekly-review-template.md` - Detailed weekly review structure
- `references/morning-planning.md` - Morning planning best practices
**Load references when:**
- Weekly review preparation
- User asks about reflection techniques
- Customizing review workflows

210
skills/knowledge-management/SKILL.md
View File

@@ -1,210 +0,0 @@
---
name: knowledge-management
description: "Knowledge base and note management with Obsidian. Use when: (1) saving information for later, (2) organizing notes and references, (3) finding past notes, (4) building knowledge connections, (5) managing documentation. Triggers: save this, note, remember, knowledge base, where did I put, find my notes on, documentation."
compatibility: opencode
---
# Knowledge Management
Note capture and knowledge organization using Obsidian as the backend.
## Status: Active
Quick note capture and knowledge organization using Obsidian markdown vault.
## Quick Note Capture
- Minimal friction capture to Obsidian vault (~/CODEX/)
- Auto-tagging based on content
- Link to related notes using WikiLinks
- Use frontmatter for metadata
## Knowledge Retrieval
- Fast search using ripgrep across vault
- Tag-based filtering (#tag syntax)
- WikiLink connections for related notes
- Use Obsidian graph view for visual connections
## Resource Organization
- PARA Resources category management (03-resources/)
- Topic clustering with folders
- Archive maintenance (04-archive/)
- Frontmatter for structured metadata
## Documentation Management
- Technical docs organization
- Version tracking via Git
- Cross-reference linking
- Template-driven structure
## Integration Points
- **Obsidian**: Primary storage (Markdown vault at ~/CODEX/)
- **task-management**: Link notes to projects/areas
- **research**: Save research findings to Resources
## Quick Commands
| Command | Description |
|---------|-------------|
| `note: [content]` | Quick capture to inbox |
| `find notes on [topic]` | Search vault with ripgrep |
| `link [note] to [note]` | Create WikiLink connection |
| `organize [tag/topic]` | Cluster related notes |
## Note Structure
### Quick Note Format
```markdown
---
date: 2026-01-27
created: 2026-01-27T18:30:00Z
type: note
tags: #quick-capture #{{topic_tag}}
---
# {{topic}}
## Content
{{note content}}
## Related
- [[Related Note 1]]
- [[Related Note 2]]
```
### Resource Format
```markdown
---
date: 2026-01-27
created: 2026-01-27T18:30:00Z
type: resource
tags: #{{topic}} #{{category}}
status: active
---
# {{topic}}
## Overview
{{brief description}}
## Key Information
- Point 1
- Point 2
- Point 3
## Resources
- [Link 1](https://...)
- [Link 2](https://...)
## Related Notes
- [[Note 1]]
- [[Note 2]]
```
## Storage Locations
```
~/CODEX/
├── 00-inbox/ # Quick captures
│ ├── quick-capture.md # Unprocessed notes
│ ├── web-clips.md # Saved web content
│ └── learnings.md # New learnings
├── 01-projects/ # Project-specific knowledge
├── 02-areas/ # Ongoing responsibilities
├── 03-resources/ # Reference material
│ ├── programming/
│ ├── tools/
│ ├── documentation/
│ └── brainstorms/
└── 04-archive/ # Stale content
├── projects/
├── areas/
└── resources/
```
## Search Patterns
Use ripgrep for fast vault-wide searches:
```bash
# Search by topic
rg "NixOS" ~/CODEX --type md
# Search by tag
rg "#programming" ~/CODEX --type md
# Search for links
rg "\\[\\[" ~/CODEX --type md
# Find recent notes
rg "date: 2026-01-2" ~/CODEX --type md
```
## Best Practices
1. **Capture quickly, organize later** - Don't overthink during capture
2. **Use WikiLinks generously** - Creates network effect
3. **Tag for retrieval** - Tag by how you'll search, not how you think
4. **Maintain PARA structure** - Keep notes in appropriate folders
5. **Archive regularly** - Move inactive content to 04-archive
6. **Use templates** - Consistent structure for same note types
7. **Leverage graph view** - Visual connections reveal patterns
## Templates
### Quick Capture Template
```markdown
---
date: {{date}}
created: {{timestamp}}
type: note
tags: #quick-capture
---
# {{title}}
## Notes
{{content}}
## Related
- [[]]
```
### Learning Template
```markdown
---
date: {{date}}
created: {{timestamp}}
type: learning
tags: #learning #{{topic}}
---
# {{topic}}
## What I Learned
{{key insight}}
## Why It Matters
{{application}}
## References
- [Source](url)
- [[]]
```
## Integration with Other Skills
| From | To knowledge-management | Trigger |
|------|----------------------|---------|
| research | Save findings | "Save this research" |
| task-management | Link to projects/areas | "Note about project X" |
| brainstorming | Save brainstorm | "Save this brainstorm" |
| daily-routines | Process inbox | "Weekly review" |
## Notes
Expand based on actual note-taking patterns. Consider integration with mem0-memory skill for AI-assisted recall.

338
skills/meeting-notes/SKILL.md
View File

@@ -1,338 +0,0 @@
---
name: meeting-notes
description: "Structured meeting note capture and action item extraction. Use when: (1) taking meeting notes, (2) starting a meeting, (3) processing raw meeting notes, (4) extracting action items. Triggers: meeting, notes, attendies, action items, follow up."
compatibility: opencode
---
# Meeting Notes
Structured meeting note creation with action item tracking for Chiron system.
## Meeting Creation
**When user says**: "Start meeting: X", "Meeting about X", "Take meeting notes for X"
**Steps:**
1. **Determine meeting type**
- Standup (daily/weekly sync)
- 1:1 meeting
- Workshop/brainstorm
- Decision meeting
2. **Create meeting note using template**
- Template: `_chiron/templates/meeting.md`
- Location: Depends on context
- Project-specific: `01-projects/[work|personal]/[project]/meetings/[topic]-YYYYMMDD.md`
- Area-related: `02-areas/[area]/meetings/[topic]-YYYYMMDD.md`
- General: `00-inbox/meetings/[topic]-YYYYMMDD.md`
3. **Fill in sections:**
- Title, date, time, duration
- Attendees (names and roles)
- Agenda (if known in advance)
- Notes (during or after)
- Decisions made
- Action items
4. **Create action item tasks**
- Extract each action item
- Create as tasks in note (Obsidian Tasks format)
- Assign owners and due dates
- Link to related projects/areas
5. **Link to context**
- Link to project if meeting was about project
- Link to area if about area
- Link to related resources
**Output format:**
```markdown
---
title: "Meeting Title"
date: 2026-01-27
time: "14:00-15:00"
duration: "1 hour"
location: [Zoom/Office/etc.]
attendees: [Person 1, Person 2]
type: [standup|1:1|workshop|decision]
project: [[Project Name]]
tags: [meeting, work]
---
## Attendees
- [Name] - [Role] - [Organization]
- [Name] - [Role] - [Organization]
## Agenda
1. [Item 1]
2. [Item 2]
3. [Item 3]
## Notes
### [Item 1]
- [Key point 1]
- [Key point 2]
### [Item 2]
- [Key point 1]
- [Key point 2]
## Decisions Made
1. [Decision 1] - [reasoning]
2. [Decision 2] - [reasoning]
## Action Items
- [ ] [Action description] #meeting #todo 🔼 👤 @name 📅 YYYY-MM-DD
- [ ] [Action description] #meeting #todo 🔼 👤 @self 📅 YYYY-MM-DD
- [ ] [Action description] #meeting #todo 🔽 👤 @name 📅 YYYY-MM-DD
## Next Steps
- [ ] Schedule follow-up meeting
- [ ] Share notes with team
```
## Processing Raw Notes
**When user says**: "Process these meeting notes", "Clean up meeting notes", [provides raw text]
**Steps:**
1. **Parse raw text for:**
- Attendees (people mentioned)
- Action items (next steps, to-dos, action points)
- Decisions (agreed, decided, resolved)
- Key topics/themes
2. **Structure into template**
- Create meeting note with proper sections
- Extract action items as tasks
- Identify decisions made
3. **Link to context**
- Detect mentions of projects/areas
- Create wiki-links automatically
- Add appropriate tags
4. **Confirm with user**
- Show extracted structure
- Ask for corrections
- Finalize note
**Example:**
```
User provides raw notes:
"Met with John and Sarah about Q1 roadmap. Decided to prioritize feature A over B. John to talk to engineering. Sarah to create PRD. Next meeting next Tuesday."
Action:
Create meeting note:
---
title: "Q1 Roadmap Discussion"
attendees: [John, Sarah]
type: decision
---
## Decisions Made
1. Prioritize feature A over B - Resource constraints
## Action Items
- [ ] Talk to engineering about timeline #meeting #todo 🔼 👤 @john 📅 2026-02-03
- [ ] Create PRD for feature A #meeting #todo 🔼 👤 @sarah 📅 2026-02-05
## Next Steps
- [ ] Schedule follow-up next Tuesday
Confirm: "Created meeting note with 2 action items assigned to John and Sarah."
```
## Action Item Extraction
**When user says**: "Extract action items", "What are the action items?", [shows meeting note]
**Steps:**
1. **Read meeting note**
2. **Extract action items section**
3. **Parse each action item:**
- Task description
- Owner (@mention)
- Due date (📅 date)
- Priority (⏫/🔼/🔽)
- Tags
4. **Present summary:**
- Total action items
- Grouped by owner
- Highlight overdue items
**Output format:**
```markdown
## Action Items Summary
Total: 5 items
### Assigned to @john
- [ ] Task 1 🔼 📅 2026-01-30
- [ ] Task 2 ⏫ 📅 2026-01-28
### Assigned to @sarah
- [ ] Task 3 🔼 📅 2026-02-05
### Unassigned
- [ ] Task 4 🔽
### Overdue
- [ ] Task 2 ⏫ 📅 2026-01-27 (DUE TODAY)
```
## Meeting Follow-Up
**When user says**: "Follow up on meeting", "Check action items", "What's outstanding from X meeting?"
**Steps:**
1. **Find meeting note** (by title, date, or attendee)
2. **Check action items status**
3. **Generate follow-up note**:
- Completed items
- Incomplete items
- Blockers or delays
- Next actions
**Output format:**
```markdown
# Follow-Up: [Meeting Title]
## Completed Items ✅
- [x] Task 1 - Completed on 2026-01-26
- [x] Task 2 - Completed on 2026-01-27
## Incomplete Items ⏭️
- [ ] Task 3 - Blocked: Waiting for approval
- [ ] Task 4 - In progress
## Recommended Next Actions
- [ ] Follow up with @john on Task 3
- [ ] Check Task 4 progress on Wednesday
- [ ] Schedule next meeting
```
## Meeting Types
### Standup
**Duration**: 15-30 minutes
**Purpose**: Sync, blockers, quick updates
**Template variation**: Minimal notes, focus on blockers and today's plan
### 1:1 Meeting
**Duration**: 30-60 minutes
**Purpose**: In-depth discussion, problem-solving
**Template variation**: Detailed notes, multiple action items
### Workshop/Brainstorm
**Duration**: 1-3 hours
**Purpose**: Idea generation, collaboration
**Template variation**: Focus on ideas, themes, next steps (few action items)
### Decision Meeting
**Duration**: 30-60 minutes
**Purpose**: Make decisions on specific topics
**Template variation**: Emphasize decisions, reasoning, action items
## Integration with Other Skills
**Delegates to:**
- `obsidian-management` - Create/update meeting notes
- `task-management` - Extract action items as tasks
- `chiron-core` - Link to projects/areas
- `calendar-scheduling` - Schedule follow-up meetings
- `quick-capture` - Quick capture mode during meetings
**Delegation rules:**
- File operations → `obsidian-management`
- Task operations → `task-management`
- PARA linkage → `chiron-core`
- Calendar actions → `calendar-scheduling`
## Best Practices
### During Meeting
- Focus on decisions and action items
- Capture attendees and roles
- Note dates/times for reference
- Link to relevant projects immediately
### After Meeting
- Extract action items within 24 hours
- Share notes with attendees
- Schedule follow-ups if needed
- Link note to daily note (tagged with #meeting)
### Action Items
- Be specific (not vague like "follow up")
- Assign owners clearly (@mention)
- Set realistic due dates
- Set appropriate priorities
- Link to related work
## File Naming
**Pattern:** `[topic]-YYYYMMDD.md`
**Examples:**
- `product-roadmap-20260127.md`
- `standup-team-20260127.md`
- `feature-planning-20260127.md`
- `decision-budget-20260127.md`
## Template Variables
**Replace in `_chiron/templates/meeting.md`:**
| Variable | Replacement |
|----------|-------------|
| `{{title}}` | Meeting title |
| `{{date}}` | Meeting date (YYYY-MM-DD) |
| `{{time}}` | Meeting time (HH:mm) |
| `{{attendees}}` | Attendee list |
| `{{type}}` | Meeting type |
| `{{project}}` | Linked project |
## Error Handling
### Ambiguous Attendees
1. Ask for clarification
2. Offer to use generic names (e.g., "Team", "Design Team")
3. Note that owner is unclear
### No Action Items
1. Confirm with user
2. Ask: "Any action items from this meeting?"
3. If no, note as informational only
### Duplicate Meeting Notes
1. Search for similar meetings
2. Ask user: "Merge or create new?"
3. If merge, combine information appropriately
## Quick Reference
| Action | Command Pattern |
|--------|-----------------|
| Start meeting | "Meeting: [topic]" or "Start meeting: [title]" |
| Process notes | "Process meeting notes: [raw text]" |
| Extract actions | "Extract action items from meeting" |
| Follow up | "Follow up on meeting: [title]" or "Check action items" |
| Find meeting | "Find meeting about [topic]" |
## Resources
- `references/meeting-formats.md` - Different meeting type templates
- `references/action-item-extraction.md` - Patterns for detecting action items
**Load references when:**
- Customizing meeting templates
- Processing raw meeting notes
- Troubleshooting extraction issues

558
skills/meeting-notes/references/teams-transcript-workflow.md
View File

@@ -1,558 +0,0 @@
# Teams Transcript Processing Workflow
Manual workflow for processing Teams meeting transcripts (.docx) into structured meeting notes with action items.
## Table of Contents
1. [Workflow Overview](#workflow-overview)
2. [Prerequisites](#prerequisites)
3. [Step-by-Step Process](#step-by-step-process)
4. [Templates](#templates)
5. [Integration Points](#integration-points)
6. [Best Practices](#best-practices)
7. [Troubleshooting](#troubleshooting)
---
## Workflow Overview
```
Teams Transcript (.docx)
↓
[Manual: Upload transcript]
↓
[Extract text content]
↓
[AI Analysis: Extract key info]
├─→ Attendees
├─→ Topics discussed
├─→ Decisions made
└─→ Action items
↓
[Create Obsidian meeting note]
├─→ Use meeting-notes template
├─→ Include transcript summary
└─→ Extract action items as tasks
↓
[Optional: Sync to Basecamp]
├─→ Create todos in Basecamp
└─→ Assign to project
```
---
## Prerequisites
### Tools Needed
- Teams (for recording and downloading transcripts)
- Python with `python-docx` library (for text extraction)
- Obsidian (for storing meeting notes)
- Basecamp MCP (for syncing action items - optional)
### Install Dependencies
```bash
pip install python-docx
```
---
## Step-by-Step Process
### Step 1: Download Teams Transcript
**In Teams**:
1. Go to meeting recording
2. Click "..." (more options)
3. Select "Open transcript" or "Download transcript"
4. Save as `.docx` file
5. Note filename (includes date/time)
**Filename format**: `MeetingTitle_YYYY-MM-DD_HHMM.docx`
### Step 2: Extract Text from DOCX
**Python script** (`/tmp/extract_transcript.py`):
```python
#!/usr/bin/env python3
from docx import Document
import sys
import os
def extract_transcript(docx_path):
"""Extract text from Teams transcript DOCX"""
try:
doc = Document(docx_path)
full_text = '\n'.join([para.text for para in doc.paragraphs])
return full_text
except Exception as e:
print(f"Error reading DOCX: {e}")
return None
if __name__ == "__main__":
if len(sys.argv) != 2:
print("Usage: python extract_transcript.py <transcript.docx>")
sys.exit(1)
docx_path = sys.argv[1]
text = extract_transcript(docx_path)
if text:
print(text)
# Optionally save to text file
output_path = docx_path.replace('.docx', '.txt')
with open(output_path, 'w') as f:
f.write(text)
print(f"\nExtracted to: {output_path}")
```
**Usage**:
```bash
python extract_transcript.py "MeetingName_2026-01-28_1400.docx"
```
### Step 3: AI Analysis of Transcript
**Prompt for AI** (ask your AI assistant):
```
Analyze this Teams meeting transcript and extract:
1. Attendees:
- Names and roles (if mentioned)
- Who spoke the most
- Any key stakeholders
2. Topics Discussed:
- Main topics (3-5 key items)
- Brief summary of each topic
3. Decisions Made:
- Clear decisions with reasoning
- Format: "Decision: [what] - [reasoning]"
- Include: "Deferred decisions" if applicable
4. Action Items:
- Extract specific, actionable tasks
- Include: owner (@mention), due date (if mentioned), priority (implicit from context)
- Format: "- [ ] Task description #meeting #todo 🔼 👤 @name 📅 YYYY-MM-DD"
5. Next Steps:
- Follow-up meetings needed
- Deliverables expected
- Blockers or dependencies
Format output in markdown ready for Obsidian meeting template.
```
### Step 4: Create Obsidian Meeting Note
**Ask AI to**:
- Use meeting-notes skill template
- Format extracted content
- Create proper frontmatter
- Add wiki-links to related projects/areas
**Template structure** (from meeting-notes skill):
```markdown
---
title: "[Meeting Title]"
platform: teams
date: YYYY-MM-DD
time: HH:mm-HH:mm
duration: "X minutes"
attendees: [names]
transcript_file: "MeetingName_2026-01-28.docx"
project: [[Project Name]]
tags: [meeting, work, teams]
---
## Attendees
- [Name] - [Role]
- [Name] - [Role]
## Topics Discussed
### [Topic 1]
- [Summary]
### [Topic 2]
- [Summary]
## Decisions Made
1. [Decision] - [Reasoning]
2. [Decision] - [Reasoning]
## Action Items
- [ ] [Action description] #meeting #todo 🔼 👤 @name 📅 YYYY-MM-DD
- [ ] [Action description] #meeting #todo 🔽 👤 @self 📅 YYYY-MM-DD
## Next Steps
- [ ] Schedule follow-up meeting
- [ ] Share notes with team
```
### Step 5: Save to Obsidian
**Location**:
```
~/CODEX/01-projects/work/[project]/meetings/[topic]-YYYYMMDD.md
```
**Ask AI to**:
- Determine project from context
- Create proper folder structure
- Use kebab-case for filename
- Add to project MOC
### Step 6: Sync Action Items to Basecamp (Optional)
**When to sync**:
- Meeting was about a specific project
- Action items have clear owners
- Project uses Basecamp for task tracking
**Ask user**: "Sync these action items to Basecamp?"
**If yes**:
1. Delegate to basecamp skill
2. Ask: "Which Basecamp project?"
3. Create todos with:
- Proper due dates
- Assignees (from @mentions)
- Linked to project
4. Confirm: "Created X todos in [project]"
---
## Templates
### AI Analysis Prompt Template
**Copy this prompt** for consistent results:
```text
You are a meeting analysis assistant. Analyze this Teams meeting transcript and extract:
1. Attendees:
- List all participants mentioned
- Identify speakers (who talked most)
- Note any key stakeholders (managers, decision-makers)
2. Topics Discussed (3-5 main topics):
For each topic:
- Title (2-4 words)
- Summary (2-3 sentences)
- Time spent on topic (if discernible from transcript)
3. Decisions Made:
For each decision:
- Decision statement (what was decided)
- Reasoning (brief justification)
- Consensus level (unanimous / majority / proposed)
- Format as checklist item: `- [ ] Decision: [text]`
4. Action Items:
For each action item:
- Description (specific, actionable verb)
- Owner (@mention if clear, otherwise "Unassigned")
- Due date (YYYY-MM-DD if mentioned, else "No deadline")
- Priority (implicit: ⏫ urgent, 🔼 high, 🔽 low)
- Format: `- [ ] Task #meeting #todo [priority] 👤 @owner 📅 date`
5. Next Steps:
- Follow-up meetings needed?
- Deliverables expected?
- Blockers or dependencies?
**Output Format**: Markdown ready for Obsidian meeting note template.
**Meeting Type**: [standup / 1:1 / workshop / decision]
Transcript:
[PASTE TEAMS TRANSCRIPT HERE]
```
### Meeting Note Template (Enhanced for Teams)
```markdown
---
title: "[Meeting Title]"
platform: teams
date: YYYY-MM-DD
time: HH:mm-HH:mm
duration: "X minutes"
attendees: [Name 1 - Role, Name 2 - Role, ...]
transcript_file: "transcripts/[Topic]-YYYYMMDD.docx"
recording_link: "[Teams recording URL if available]"
project: [[Project Name]]
tags: [meeting, work, teams, transcript]
---
## Attendees
| Name | Role | Company |
|-------|-------|---------|
| [Name] | [Role] | [Company] |
| [Name] | [Role] | [Company] |
## Agenda
[If agenda was known in advance]
1. [Item 1]
2. [Item 2]
3. [Item 3]
## Transcript Summary
[AI-generated summary of transcript]
## Topics Discussed
### [Topic 1]
- [Summary points]
- [Time spent: X minutes]
### [Topic 2]
- [Summary points]
- [Time spent: X minutes]
## Decisions Made
1. ✅ [Decision 1]
- **Reasoning**: [Why this decision]
- **Owner**: [Who made decision]
- **Due**: [If applicable]
2. ✅ [Decision 2]
- **Reasoning**: [Why this decision]
- **Owner**: [Who made decision]
### Deferred Decisions
- [ ] [Decision deferred] - [Why deferred, revisit date]
## Action Items
- [ ] [Task 1] #meeting #todo 🔼 👤 @owner 📅 YYYY-MM-DD
- [ ] [Task 2] #meeting #todo ⏫ 👤 @owner 📅 YYYY-MM-DD
- [ ] [Task 3] #meeting #todo 🔽 👤 self 📅 YYYY-MM-DD
### Action Item Summary
| Task | Owner | Due | Priority |
|-------|--------|------|----------|
| [Task 1] | @owner | YYYY-MM-DD | ⏫ |
| [Task 2] | @owner | YYYY-MM-DD | 🔼 |
| [Task 3] | @self | N/A | 🔽 |
## Next Steps
- [ ] Schedule follow-up meeting: [Topic] - [Proposed date]
- [ ] Share notes with: [attendee list]
- [ ] Update project status in Basecamp
## Notes
[Additional notes, observations, or clarifications]
## Links
- 📹 Teams Recording: [URL if available]
- 📄 Transcript: [[transcript_filename]]
- 🗄 Project: [[Project Name]]
- 📄 Related Docs: [[Related Outline Doc]](outline://document/abc123)
```
---
## Integration Points
### With meeting-notes Skill
**Flow**:
```
User: "Process transcript: [file.docx]"
1. Extract text from DOCX
2. Ask AI to analyze transcript
3. AI extracts: attendees, topics, decisions, action items
4. Create meeting note using meeting-notes skill
5. Ask: "Sync action items to Basecamp?"
```
### With basecamp Skill
**Flow** (optional):
```
User: "Yes, sync to Basecamp"
1. Ask: "Which Basecamp project?"
2. List available projects
3. For each action item:
- create_todo(project_id, todolist_id, content, due_on, assignee_ids)
4. Confirm: "Created X todos in [project]"
```
### With obsidian-management Skill
**Flow**:
```
1. Create meeting note at: 01-projects/work/[project]/meetings/[topic]-YYYYMMDD.md
2. Update project MOC with link to meeting:
- Add to "Meetings" section in project _index.md
3. If decision made, create in decisions/ folder
4. If applicable, export decision to Outline wiki
```
---
## Best Practices
### During Meeting
1. **Use Teams recording**: Get transcript automatically
2. **Name attendees**: Add their roles to transcript
3. **Speak clearly**: Improves transcript accuracy
4. **Agenda first**: Helps AI structure analysis
### Processing Transcripts
1. **Process quickly**: Within 24 hours while fresh
2. **Clean up text**: Remove filler words (um, ah, like)
3. **Be specific**: Action items must be actionable, not vague
4. **Assign owners**: Every action item needs @mention
5. **Set due dates**: Even if approximate (next week, by next meeting)
### Storage
1. **Consistent location**: All work meetings in project/meetings/
2. **Link everything**: Link to project, related docs, areas
3. **Tag properly**: #meeting, #work, #teams, #transcript
4. **Archive old**: Move completed project meetings to archive/
### Basecamp Sync
1. **Sync important meetings**: Not every meeting needs sync
2. **Use project context**: Sync to relevant project
3. **Verify in Basecamp**: Check todos were created correctly
4. **Follow up**: Check completion status regularly
---
## Troubleshooting
### Transcript Won't Open
**Problem**: DOCX file corrupted or wrong format
**Solution**:
1. Re-download from Teams
2. Try opening in Word first to verify
3. Use alternative: Copy-paste text manually
### AI Misses Action Items
**Problem**: Transcript analysis misses clear action items
**Solution**:
1. Manually add missed items to meeting note
2. Reprompt AI with specific context: "Review transcript again, focus on action items"
3. Check transcript: Was the audio clear?
### Wrong Project Assigned
**Problem**: Meeting note created in wrong project folder
**Solution**:
1. Move file to correct location
2. Update links in project MOCs
3. Use consistent naming conventions
### Basecamp Sync Fails
**Problem**: Todos not created in Basecamp
**Solution**:
1. Check Basecamp MCP is connected
2. Verify project ID is correct
3. Check assignee IDs are valid
4. Check todo list exists in project
5. Retry with fewer items
---
## Example End-to-End
### Input
**Teams transcript**: `api-design-review_2026-01-28_1400.docx`
### AI Output
```markdown
## Attendees
- Alice (Product Owner)
- Bob (Lead Developer)
- Charlie (Tech Lead)
- Sarah (UX Designer)
## Topics Discussed
1. API Authentication Design (20 min)
2. Rate Limiting Strategy (15 min)
3. Error Handling (10 min)
## Decisions Made
1. Use OAuth2 with refresh tokens - Industry standard, better security
2. Implement 1000 req/min rate limit - Based on load tests
## Action Items
- [ ] Create OAuth2 implementation guide #meeting #todo 🔼 👤 @alice 📅 2026-02-05
- [ ] Document rate limiting policy #meeting #todo 🔼 👤 @bob 📅 2026-02-10
- [ ] Update error handling documentation #meeting #todo 🔽 👤 @sarah 📅 2026-02-15
```
### Obsidian Note Created
**File**: `~/CODEX/01-projects/work/api-integration-platform/meetings/api-design-review-20260128.md`
### Basecamp Sync
**Project**: API Integration Platform
**Todos created**: 3
- OAuth2 guide (assigned to Alice, due 2026-02-05)
- Rate limiting (assigned to Bob, due 2026-02-10)
- Error handling (assigned to Sarah, due 2026-02-15)
---
## Automation (Future n8n Implementation)
When n8n is added, automate:
1. **Watch transcript folder**: Auto-trigger on new .docx files
2. **AI auto-analysis**: Use AI API to extract meeting info
3. **Auto-create meeting notes**: Save to Obsidian automatically
4. **Auto-sync to Basecamp**: Create todos for action items
5. **Send notifications**: "Meeting processed, X action items created"
**Workflow diagram**:
```
Teams transcript folder
↓ (n8n: Watch folder)
[Trigger: new .docx]
↓
[Extract text]
↓
[AI Analysis]
↓
[Create meeting note]
↓
[Sync to Basecamp] (conditional)
↓
[Send ntfy notification]
```
---
## Quick Reference
| Action | Tool/Script |
|--------|--------------|
| Download transcript | Teams UI |
| Extract text | python extract_transcript.py |
| Analyze transcript | AI assistant prompt |
| Create meeting note | meeting-notes skill |
| Sync to Basecamp | basecamp skill |
| Store in Obsidian | obsidian-management skill |
| Export decision | outline skill (optional) |

241
skills/msteams/SKILL.md
View File

@@ -1,241 +0,0 @@
---
name: msteams
description: "Microsoft Teams Graph API integration for team communication and collaboration. Use when Opencode needs to interact with Teams for: (1) Managing channels and teams, (2) Sending and retrieving channel messages, (3) Creating and managing meetings, (4) Handling chat conversations, (5) Building automated team communication workflows. Triggers: 'Teams', 'channel', 'meeting', 'chat', 'team message', 'Microsoft Teams'."
compatibility: opencode
---
# Microsoft Teams Graph API Integration
Integrate with Microsoft Teams via Graph API for team communication, meeting management, and collaboration workflows.
## Quick Start
Teams Graph API provides comprehensive access to Teams functionality for automation workflows. Use this skill when building workflows that involve:
- Automated channel message posting
- Meeting scheduling and management
- Chat interaction and conversation handling
- Team and channel organization
## Core API Capabilities
### Teams & Channels
**List teams**
- Get all teams the user has access to
- Filter teams by display name or group ID
- Retrieve team membership and role information
**Access channels**
- Get all channels within a team
- Access standard channels, private channels, and shared channels
- Retrieve channel membership and settings
**Manage channels**
- Create new channels in teams
- Update channel properties (name, description)
- Archive or delete channels
- Manage channel members and permissions
### Channel Messages
**Send messages**
- Post new messages to channels
- Send rich text and formatted content
- Attach files and images to messages
- Mention users or teams with @mentions
- Create adaptive cards for interactive messages
**Retrieve messages**
- Get channel message history
- Filter messages by date range or sender
- Load message replies and threads
- Access message attachments and reactions
**Manage messages**
- Edit existing channel messages
- Delete messages
- Pin important messages
- Add reactions and reactions management
### Meetings
**Create meetings**
- Schedule online meetings via Teams
- Set meeting title, description, and duration
- Add participants and attendees
- Configure meeting options (recording, lobby, etc.)
**Manage meetings**
- Update meeting details
- Cancel meetings
- Get meeting recordings and transcripts
- Access meeting attendance reports
**Meeting participation**
- Join meetings via API (where supported)
- Get meeting links and join URLs
- Manage meeting chat during calls
### Chat Conversations
**List chats**
- Get all chats the user participates in
- Filter by chat type (1:1, group, meeting)
- Access chat metadata and participant info
**Send chat messages**
- Send messages to 1:1 or group chats
- Send rich text and formatted content
- Attach files to chat messages
**Retrieve chat messages**
- Get chat message history
- Load message threads and replies
- Access message attachments and metadata
**Manage chats**
- Create new group chats
- Add or remove participants
- Update chat settings
- Archive or delete conversations
## Common Workflows
### Automated Channel Announcements
Broadcast information to team channels:
1. Identify target team and channel via Graph API
2. Prepare message content with rich text formatting
3. Post message to channel using message endpoint
4. Include attachments if needed
5. Log or track message delivery
### Meeting Scheduling Automation
Schedule recurring or one-off meetings:
1. Create meeting object with required details
2. Add attendees and configure options
3. Use Graph API to create meeting in calendar
4. Generate and share meeting link
5. Send confirmation to participants
### Chat-Based Notifications
Send notifications to users or groups via chat:
1. Identify target chat (1:1 or group)
2. Compose notification message
3. Send via chat message endpoint
4. Handle delivery confirmations
5. Track response if needed
### Content Retrieval & Reporting
Gather information from Teams conversations:
1. Query channel or chat message history
2. Filter by date, sender, or keywords
3. Extract relevant content and attachments
4. Compile report or summary
5. Format for user consumption
### Meeting Follow-up Workflows
Automate post-meeting actions:
1. Retrieve meeting transcripts or recordings
2. Extract action items or decisions
3. Create follow-up tasks or messages
4. Share summary with participants
5. Schedule next meeting if needed
## API Endpoint Reference
**Teams & Channels**
- `GET /teams` - List all teams
- `GET /teams/{team-id}` - Get specific team
- `GET /teams/{team-id}/channels` - List team channels
- `GET /teams/{team-id}/channels/{channel-id}` - Get channel details
- `POST /teams/{team-id}/channels` - Create new channel
- `PATCH /teams/{team-id}/channels/{channel-id}` - Update channel
**Channel Messages**
- `GET /teams/{team-id}/channels/{channel-id}/messages` - List messages
- `GET /teams/{team-id}/channels/{channel-id}/messages/{message-id}` - Get message
- `POST /teams/{team-id}/channels/{channel-id}/messages` - Send message
- `PATCH /teams/{team-id}/channels/{channel-id}/messages/{message-id}` - Edit message
- `DELETE /teams/{team-id}/channels/{channel-id}/messages/{message-id}` - Delete message
**Meetings**
- `POST /me/onlineMeetings` - Create online meeting
- `GET /me/onlineMeetings` - List my meetings
- `GET /me/onlineMeetings/{meeting-id}` - Get meeting details
- `PATCH /me/onlineMeetings/{meeting-id}` - Update meeting
- `DELETE /me/onlineMeetings/{meeting-id}` - Cancel meeting
- `GET /me/onlineMeetings/{meeting-id}/transcripts` - Get transcripts
**Chat**
- `GET /chats` - List all chats
- `GET /chats/{chat-id}` - Get chat details
- `POST /chats` - Create new chat
- `GET /chats/{chat-id}/messages` - List chat messages
- `POST /chats/{chat-id}/messages` - Send chat message
## Best Practices
**Message Formatting**
- Use Markdown or HTML for rich text when supported
- Handle @mentions correctly (user or team references)
- Validate message length limits (typically 28KB)
- Test adaptive cards for compatibility
**Rate Limiting**
- Respect Microsoft Graph API rate limits
- Implement exponential backoff for throttling
- Batch operations where possible
- Monitor API usage and adjust accordingly
**Error Handling**
- Handle 404 errors (resource not found)
- Manage permission errors (403) gracefully
- Implement retry logic for transient failures
- Log errors with sufficient context for debugging
**Meeting Management**
- Check participant limits for meeting type
- Validate meeting options before creation
- Handle time zone conversions correctly
- Confirm meeting creation before sharing links
**Content Safety**
- Validate content for sensitive information
- Follow organizational communication policies
- Respect privacy when accessing chat history
- Obtain consent where required for automation
## Integration Examples
**Post a daily status update to channel**
1. Identify target channel ID via teams/channels endpoints
2. Compose status message with relevant data
3. Use `POST /teams/{team-id}/channels/{channel-id}/messages`
4. Include attachments or adaptive cards if needed
5. Confirm successful posting
**Schedule a weekly team meeting**
1. Create meeting object with recurring schedule
2. Add team members as attendees
3. Call `POST /me/onlineMeetings`
4. Extract meeting link and share with team
5. Send confirmation via channel or chat
**Send notification to multiple users via group chat**
1. Create group chat with participants
2. Compose notification message
3. Send via `POST /chats/{chat-id}/messages`
4. Track delivery and responses
5. Archive or update chat as needed
**Retrieve meeting action items**
1. Get meeting transcript via `/transcripts` endpoint
2. Parse transcript for action items
3. Create follow-up tasks or messages
4. Share summary with participants
5. Update project tracking systems if integrated

403
skills/obsidian-management/SKILL.md
View File

@@ -1,403 +0,0 @@
---
name: obsidian-management
description: "Obsidian vault operations and file management for ~/CODEX. Use when: (1) creating/editing notes in Obsidian vault, (2) using templates from _chiron/templates/, (3) managing vault structure, (4) reading vault files, (5) organizing files within PARA structure. Triggers: obsidian, vault, note, template, create note, read note, organize files."
compatibility: opencode
---
# Obsidian Management
File operations and template usage for Obsidian vault at `~/CODEX/`.
## Vault Structure
```
~/CODEX/
├── _chiron/ # System files
│ ├── context.md # Primary context
│ └── templates/ # Note templates
├── 00-inbox/ # Quick captures
├── 01-projects/ # Active projects
├── 02-areas/ # Ongoing responsibilities
├── 03-resources/ # Reference material
├── 04-archive/ # Completed items
├── daily/ # Daily notes
└── tasks/ # Task management
```
## Core Operations
### Create Note
**When user says**: "Create a note called X", "Make a new note for X", "Add a note"
**Steps:**
1. Determine location (ask if unclear):
- `00-inbox/` for quick captures
- `01-projects/[work|personal]/[project]/` for project notes
- `02-areas/` for area notes
- `03-resources/` for reference material
2. Create file with proper filename (kebab-case, .md extension)
3. Add frontmatter if using template
4. Confirm creation
**Example:**
```
User: "Create a note about Obsidian plugins in resources"
Action:
1. Locate: ~/CODEX/03-resources/tools/obsidian-plugins.md
2. Create file with template or basic frontmatter
3. Confirm: "Created obsidian-plugins.md in 03-resources/tools/"
```
### Read Note
**When user says**: "Read the note X", "Show me X note", "What's in X?"
**Steps:**
1. Find note by:
- Exact path if provided
- Fuzzy search across vault
- Dataview query if complex
2. Read full note content
3. Summarize key points if long
4. Offer follow-up actions
**Example:**
```
User: "Read my learning-python note"
Action:
1. Search: rg "learning-python" ~/CODEX --type md
2. Read matching file
3. Present content
4. Offer: "Want to edit this? Add tasks? Link to other notes?"
```
### Edit Note
**When user says**: "Update X", "Change X to Y", "Add to X"
**Steps:**
1. Read existing note
2. Locate section to modify
3. Apply changes preserving formatting
4. Maintain frontmatter structure
5. Confirm changes
**Preserve:**
- Wiki-links `[[Note Name]]`
- Frontmatter YAML
- Task formatting
- Tags
- Dataview queries
### Use Template
**When user says**: "Create using template", "Use the X template"
**Available templates:**
| Template | Location | Purpose |
|----------|----------|---------|
| `daily-note.md` | `_chiron/templates/` | Daily planning/reflection |
| `weekly-review.md` | `_chiron/templates/` | Weekly review |
| `project.md` | `_chiron/templates/` | Project initialization |
| `meeting.md` | `_chiron/templates/` | Meeting notes |
| `resource.md` | `_chiron/templates/` | Reference material |
| `area.md` | `_chiron/templates/` | Area definition |
**Steps:**
1. Read template from `_chiron/templates/[template-name].md`
2. Replace template variables ({{date}}, {{project}}, etc.)
3. Create new file in appropriate location
4. Fill in placeholder sections
**Example:**
```
User: "Create a new project using the project template for 'Learn Rust'"
Action:
1. Read _chiron/templates/project.md
2. Replace {{project}} with "learn-rust", {{date}} with today
3. Create: ~/CODEX/01-projects/personal/learn-rust/_index.md
4. Fill in: deadline, priority, goals, etc.
```
### Search Vault
**When user says**: "Search for X", "Find notes about X", "Where's X?"
**Search methods:**
1. **Simple search**: `rg "term" ~/CODEX --type md`
2. **Tag search**: `rg "#tag" ~/CODEX --type md`
3. **Task search**: `rg "- \\[ \\]" ~/CODEX --type md`
4. **Wiki-link search**: `rg "\\[\\[.*\\]\\]" ~/CODEX --type md`
**Present results grouped by:**
- Location (Projects/Areas/Resources)
- Relevance
- Date modified
### Organize Files
**When user says**: "Organize inbox", "Move X to Y", "File this note"
**Steps:**
1. Read file to determine content
2. Consult chiron-core PARA guidance for proper placement
3. Create proper directory structure if needed
4. Move file maintaining links
5. Update wiki-links if file moved
**Example:**
```
User: "Organize my inbox"
Action:
1. List files in 00-inbox/
2. For each file:
- Read content
- Determine PARA category
- Move to appropriate location
3. Update broken links
4. Confirm: "Moved 5 files from inbox to Projects (2), Resources (2), Archive (1)"
```
## File Operations
### Paths
**Always use absolute paths:**
- `~/CODEX/` → `/home/username/knowledge/`
- Expand `~` before file operations
### Filenames
**Naming conventions:**
- Notes: `kebab-case.md` (all lowercase, hyphens)
- Projects: `project-name/` (directory with `_index.md`)
- Daily notes: `YYYY-MM-DD.md` (ISO date)
- Templates: `template-name.md` (kebab-case)
**Do NOT use:**
- Spaces in filenames
- CamelCase (use kebab-case)
- Special characters (except hyphens and underscores)
### Frontmatter
**Required fields:**
```yaml
---
title: "Note Title"
tags: [tag1, tag2]
created: YYYY-MM-DD
modified: YYYY-MM-DD
---
```
**Project frontmatter:**
```yaml
---
title: "Project Name"
status: active | on-hold | completed
deadline: YYYY-MM-DD
priority: critical | high | medium | low
tags: [work, personal]
---
```
**Task file frontmatter:**
```yaml
---
title: "Task List"
context: daily | project | area
tags: [tasks]
---
```
### Wiki-Links
**Format:** `[[Note Name]]` or `[[Note Name|Display Text]]`
**Best practices:**
- Use exact note titles
- Include display text for clarity
- Link to related concepts
- Back-link from destination notes
### Tags
**Format:** `#tagname` or `#tag/subtag`
**Common tags:**
- `#work`, `#personal`
- `#critical`, `#high`, `#low`
- `#project`, `#area`, `#resource`
- `#todo`, `#done`, `#waiting`
## Template System
### Template Variables
Replace these when using templates:
| Variable | Replacement |
|----------|-------------|
| `{{date}}` | Current date (YYYY-MM-DD) |
| `{{datetime}}` | Current datetime (YYYY-MM-DD HH:mm) |
| `{{project}}` | Project name |
| `{{area}}` | Area name |
| `{{title}}` | Note title |
| `{{week}}` | Week number (e.g., W04) |
### Template Locations
**Core templates** in `_chiron/templates/`:
- `daily-note.md` - Daily planning and reflection
- `weekly-review.md` - Weekly review structure
- `project.md` - Project initialization
- `meeting.md` - Meeting notes template
- `resource.md` - Reference material
- `area.md` - Area definition
- `learning.md` - Learning capture
### Custom Templates
**User can add** templates to `_chiron/templates/`:
1. Create new template file
2. Use variable syntax: `{{variable}}`
3. Document in `_chiron/templates/README.md`
4. Reference in obsidian-management skill
## Integration with Other Skills
**Calls to other skills:**
- `chiron-core` - PARA methodology guidance for organization
- `task-management` - Extract/update tasks from notes
- `quick-capture` - Process inbox items
- `meeting-notes` - Apply meeting template
**Delegation rules:**
- User asks about PARA → `chiron-core`
- User wants task operations → `task-management`
- User wants quick capture → `quick-capture`
- User wants meeting structure → `meeting-notes`
## File Format Standards
### Task Format (Obsidian Tasks plugin)
```markdown
- [ ] Task description #tag ⏫ 📅 YYYY-MM-DD
```
**Priority indicators:**
- ⏫ = Critical (urgent AND important)
- 🔼 = High (important, not urgent)
- 🔽 = Low (nice to have)
**Date indicators:**
- 📅 = Due date
- ⏳ = Start date
- 🛫 = Scheduled date
### Dataview Queries
```dataview
LIST WHERE status = "active"
FROM "01-projects"
SORT deadline ASC
```
```dataview
TABLE deadline, status, priority
FROM "-04-archive"
WHERE contains(tags, "#work")
SORT deadline ASC
```
### Callouts
```markdown
> [!INFO] Information
> Helpful note
> [!WARNING] Warning
> Important alert
> [!TIP] Tip
> Suggestion
> [!QUESTION] Question
> To explore
```
## Error Handling
### File Not Found
1. Search for similar filenames
2. Ask user to confirm
3. Offer to create new file
### Directory Not Found
1. Create directory structure
2. Confirm with user
3. Create parent directories as needed
### Template Not Found
1. List available templates
2. Offer to create template
3. Use basic note structure if needed
### Link Breaks After Move
1. Find all notes linking to moved file
2. Update links to new path
3. Confirm updated links count
## Best Practices
### When Creating Notes
1. Use descriptive titles
2. Add relevant tags
3. Link to related notes immediately
4. Use appropriate frontmatter
### When Editing Notes
1. Preserve existing formatting
2. Update `modified` date in frontmatter
3. Maintain wiki-link structure
4. Check for broken links
### When Organizing
1. Ask user before moving files
2. Update all links
3. Confirm final locations
4. Document changes in daily note
## Quick Reference
| Action | Command Pattern |
|--------|-----------------|
| Create note | "Create note [title] in [location]" |
| Read note | "Read [note-name]" or "Show me [note-name]" |
| Edit note | "Update [note-name] with [content]" |
| Search | "Search vault for [term]" or "Find notes about [topic]" |
| Use template | "Create [note-type] using template" |
| Organize inbox | "Organize inbox" or "Process inbox items" |
| Move file | "Move [file] to [location]" |
## Resources
- `references/file-formats.md` - Detailed format specifications
- `references/dataview-guide.md` - Dataview query patterns
- `references/link-management.md` - Wiki-link best practices
- `assets/templates/` - All template files
**Load references when:**
- User asks about format details
- Creating complex queries
- Troubleshooting link issues
- Template customization needed

484
skills/outline/SKILL.md
View File

@@ -1,484 +0,0 @@
---
name: outline
description: "Search, read, and manage Outline wiki documentation via MCP. Use when: (1) searching Outline wiki, (2) reading/exporting Outline documents, (3) creating/updating Outline docs, (4) managing collections, (5) finding wiki content. Triggers: outline, wiki, search outline, find in wiki, export document."
compatibility: opencode
---
# Outline Wiki Integration
MCP server integration for Outline wiki documentation - search, read, create, and manage wiki content.
## Quick Reference
| Action | Command Pattern |
| --------------- | -------------------------------------- |
| Search wiki | "Search Outline for [topic]" |
| Read document | "Show me [document name]" |
| Export to vault | "Export [document] to Obsidian" |
| Create doc | "Create Outline doc: [title]" |
| List collections | "Show Outline collections" |
## Core Workflows
### 1. Search Wiki
**When user says**: "Search Outline for X", "Find in wiki about X", "Outline wiki: X"
**Steps**:
```
1. search_documents(query, collection_id?, limit?, offset?)
- If collection_id provided → search in specific collection
- If no collection_id → search all collections
- Default limit: 20 results
2. Present results:
- Document titles
- Collection names
- Relevance (if available)
3. Offer actions:
- "Read specific document"
- "Export to Obsidian"
- "Find related documents"
```
**Example output**:
```
Found 5 documents matching "API authentication":
📄 Authentication Best Practices (Collection: Engineering)
📄 OAuth2 Setup Guide (Collection: Security)
📄 API Key Management (Collection: DevOps)
📄 Common Auth Errors (Collection: Troubleshooting)
Read any document or export to Obsidian?
```
### 2. Read Document
**When user says**: "Show me [document]", "What's in [document]", "Read [doc from Outline]"
**Steps**:
```
1. get_document_id_from_title(query, collection_id?)
- Search by exact title
- Return document ID
2. read_document(document_id)
- Get full markdown content
3. Present content:
- Title and metadata
- Document content (formatted)
- Collection location
- Tags (if available)
4. Offer follow-up:
- "Export to Obsidian?"
- "Find related documents?"
- "Add to project?"
```
**Example output**:
```markdown
# Authentication Best Practices
**Collection**: Engineering
**Last updated**: 2026-01-25
## OAuth2 Flow
[Document content...]
## API Keys
[Document content...]
---
📂 Export to Obsidian | 🔗 Find related | ➕ Add to project
```
### 3. Export to Obsidian
**When user says**: "Export [document] to Obsidian", "Save [wiki page] to vault"
**Steps**:
```
1. export_document(document_id)
- Get markdown content
2. Determine Obsidian location:
- If for project: `01-projects/work/[project]/notes/[doc-name].md`
- If general: `03-resources/work/wiki-mirror/[doc-name].md`
3. Add frontmatter:
---
title: "[Document Title]"
source: outline
document_id: [ID]
collection: "[Collection Name]"
tags: [work, wiki, outline]
---
4. Create file in vault
5. Link to context:
- Project: [[Project Name]]
- Related resources
6. Confirm: "Exported [document] to [location]"
```
**File naming**:
- Convert to kebab-case: `Authentication Best Practices` → `authentication-best-practices.md`
- Preserve collection hierarchy: `[collection-name]/[doc-name].md`
### 4. Create Document
**When user says**: "Create Outline doc: [title]", "Add wiki page: [title]"
**Steps**:
```
1. Ask for details:
- Collection (list available if needed)
- Content (markdown text)
- Parent document (if hierarchical)
- Publish immediately?
2. create_document(title, collection_id, text?, parent_document_id?, publish?)
3. Confirm creation:
- Document ID
- URL (if Outline has web UI)
4. Offer actions:
- "Add backlink?"
- "Create in Obsidian too?"
- "Link to project?"
```
### 5. Document Discovery
**When user says**: "Show Outline collections", "Browse wiki", "What's in [collection]?"
**Steps**:
```
1. list_collections()
- Get all collections with metadata
2. Present hierarchy:
- Collection names
- Document counts
- Colors (if set)
3. User selects collection
4. get_collection_structure(collection_id)
- Show document tree
- Hierarchical view
```
**Example output**:
```
Outline Wiki Collections:
📁 Engineering (15 docs)
├─ API Documentation (8 docs)
└─ System Design (7 docs)
📁 Product (12 docs)
├─ Features (6 docs)
└─ User Guides (6 docs)
📁 Security (8 docs)
Browse which collection?
```
### 6. AI-Powered Search
**When user says**: "Ask Outline about X", "What does Outline say about X?"
**Steps**:
```
1. ask_ai_about_documents(question, collection_id?, document_id?)
- Natural language query
- AI searches across documents
2. Present AI answer:
- Summary of findings
- Source documents referenced
- Confidence (if available)
3. Offer:
- "Read source documents"
- "Export to Obsidian"
```
**Example output**:
```
🤖 Answer from Outline wiki:
Based on 12 documents, here's what I found about API authentication:
**Summary**:
- OAuth2 is preferred over API keys
- Tokens expire after 30 days
- Refresh tokens allow seamless re-authentication
**Key Sources**:
1. OAuth2 Setup Guide (Engineering/Security)
2. Authentication Best Practices (Engineering)
3. Token Management (DevOps)
Read any source document?
```
## Tool Reference
### Search & Discovery
- `search_documents(query, collection_id?, limit?, offset?)`
- Full-text search across wiki
- Optional: Scope to specific collection
- Pagination support
- `list_collections()`
- Get all collections with metadata
- Names, descriptions, colors, doc counts
- `get_collection_structure(collection_id)`
- Hierarchical document tree
- Parent-child relationships
- `get_document_id_from_title(query, collection_id?)`
- Find document by title
- Exact or fuzzy match
### Document Reading
- `read_document(document_id)`
- Full document content
- Markdown format
- Metadata included
- `export_document(document_id)`
- Export as markdown
- Same content as read_document
- Designed for exports
### Document Management
- `create_document(title, collection_id, text?, parent_document_id?, publish?)`
- Create new wiki page
- Support for hierarchical docs
- Draft or published
- `update_document(document_id, title?, text?, append?)`
- Update existing document
- Append mode for additions
- Preserve history
- `move_document(document_id, collection_id?, parent_document_id?)`
- Move between collections
- Reorganize hierarchy
### Document Lifecycle
- `archive_document(document_id)`
- Archive (not delete)
- Can be restored
- `unarchive_document(document_id)`
- Restore from archive
- `delete_document(document_id, permanent?)`
- Move to trash or permanent delete
- Requires careful confirmation
### Comments & Collaboration
- `add_comment(document_id, text, parent_comment_id?)`
- Add threaded comments
- Support for replies
- `list_document_comments(document_id, include_anchor_text?, limit?, offset?)`
- View discussion on document
- Threaded view
- `get_document_backlinks(document_id)`
- Find documents linking here
- Useful for context
### Collection Management
- `create_collection(name, description?, color?)`
- Create new collection
- For organizing docs
- `update_collection(collection_id, name?, description?, color?)`
- Edit collection metadata
- `delete_collection(collection_id)`
- Remove collection
- Affects all documents in it
- `export_collection(collection_id, format?)`
- Export entire collection
- Default: outline-markdown
- `export_all_collections(format?)`
- Export all wiki content
- Full backup
### Batch Operations
- `batch_create_documents(documents)`
- Create multiple docs at once
- For bulk imports
- `batch_update_documents(updates)`
- Update multiple docs
- For maintenance
- `batch_move_documents(document_ids, collection_id?, parent_document_id?)`
- Move multiple docs
- Reorganization
### AI-Powered
- `ask_ai_about_documents(question, collection_id?, document_id?)`
- Natural language queries
- AI-powered search
- Synthesizes across documents
## Integration with Other Skills
| From Skill | To Outline |
| ----------- | ---------- |
| meeting-notes | Export decisions to wiki |
| project-structures | Link project docs to wiki |
| daily-routines | Capture learnings in wiki |
| brainstorming | Save decisions to wiki |
## Integration with Obsidian
### Export Workflow
**When to export**:
- Important decisions made
- Project documentation needed offline
- Wiki content to reference locally
- Job transition (export all)
**Export locations**:
```
~/CODEX/
├── 01-projects/work/
│ └── [project]/
│ └── notes/
│ └── [exported-doc].md # Linked to project
└── 03-resources/work/
└── wiki-mirror/
├── [collection-name]/
│ └── [doc].md # Exported wiki pages
└── _wiki-index.md # Index of all exports
```
**Wiki index structure**:
```markdown
---
title: "Outline Wiki Index"
source: outline
last_sync: YYYY-MM-DD
---
## Collections
- [Engineering](engineering/) - 15 docs
- [Product](product/) - 12 docs
- [Security](security/) - 8 docs
## Recently Exported
- [[OAuth2 Setup Guide]] - 2026-01-25
- [[API Documentation]] - 2026-01-24
- [[System Design]] - 2026-01-23
## Search Wiki
<!-- Use outline MCP for live search -->
"Search Outline for..." → outline skill
```
## Access Control Notes
If Outline MCP is configured with `OUTLINE_READ_ONLY=true`:
- ❌ Cannot create documents
- ❌ Cannot update documents
- ❌ Cannot move/archive/delete
- ✅ Can search and read
- ✅ Can export documents
If `OUTLINE_DISABLE_DELETE=true`:
- ✅ Can create and update
- ❌ Cannot delete (protects against accidental loss)
## Work vs Personal Usage
### Work Wiki (Primary)
- Collections: Engineering, Product, Security, etc.
- Export to: `03-resources/work/wiki-mirror/`
- Projects link to: `[[Engineering/Design Decisions]]`
### Personal Wiki (Optional)
- Collections: Recipes, Travel, Hobbies, etc.
- Export to: `03-resources/personal/wiki/`
- Separate from work content
## Best Practices
### Searching
- Use specific keywords (not "everything about X")
- Use collection_id for focused search
- Check multiple collections if first search is limited
### Exporting
- Export decisions, not just reference docs
- Link exported docs to projects immediately
- Update wiki index after export
- Regular exports for offline access
### Creating Documents
- Use clear, descriptive titles
- Add to appropriate collection
- Link related documents
- Add tags for discoverability
### AI Queries
- Ask specific questions (not "everything about X")
- Use collection_id to scope query
- Verify AI sources by reading docs
- Use AI to synthesize, not replace reading
## Error Handling
### Document Not Found
1. Check title spelling
2. Try fuzzy search
3. Search collection directly
### Collection Not Found
1. List all collections
2. Check collection name
3. Verify access permissions
### Export Failed
1. Check Obsidian vault path
2. Verify disk space
3. Check file permissions
4. Create directories if needed
### Rate Limiting
- Outline MCP handles automatically with retries
- Reduce concurrent operations if persistent errors
## Quick Reference
| Action | Command Pattern |
|--------|-----------------|
| Search wiki | "Search Outline for [topic]" |
| Read document | "Show me [document name]" |
| Export to vault | "Export [document] to Obsidian" |
| Create doc | "Create Outline doc: [title]" |
| List collections | "Show Outline collections" |
| AI query | "Ask Outline about [question]" |
| Browse structure | "Browse wiki" or "Show Outline collections" |
## Resources
- `references/outline-workflows.md` - Detailed workflow examples
- `references/export-patterns.md` - Obsidian integration patterns
**Load references when**:
- Designing complex exports
- Troubleshooting integration issues
- Setting up project-to-wiki links

524
skills/outline/references/export-patterns.md
View File

@@ -1,524 +0,0 @@
# Export Patterns
Patterns and examples for exporting Outline wiki content to Obsidian vault.
## Table of Contents
1. [Frontmatter Patterns](#frontmatter-patterns)
2. [Folder Structure](#folder-structure)
3. [Linking Strategies](#linking-strategies)
4. [Index Management](#index-management)
5. [Batch Operations](#batch-operations)
---
## Frontmatter Patterns
### Standard Export Frontmatter
```yaml
---
title: "Document Title"
source: outline
document_id: "abc123def456"
collection: "Engineering/Security"
collection_id: "col_789"
tags: [work, wiki, outline, security]
outline_url: "https://outline.example.com/doc/abc123"
created_at: "2026-01-28"
exported_at: "2026-01-28"
last_updated: "2026-01-25"
---
```
### Decision Document Frontmatter
```yaml
---
title: "API Authentication Decision"
source: outline
type: decision
decision_date: "2026-01-28"
made_by: "Team Name"
decision_status: active | implemented | archived
tags: [work, wiki, decision, api, security]
---
# Decision
Use OAuth2 for all external API integrations.
```
### Process Document Frontmatter
```yaml
---
title: "API Onboarding Process"
source: outline
type: process
version: "2.1"
last_reviewed: "2026-01-28"
tags: [work, wiki, process, onboarding]
---
# API Onboarding Process
Step-by-step guide for new API consumers...
```
### Reference Document Frontmatter
```yaml
---
title: "OAuth2 Setup Guide"
source: outline
type: reference
language: "markdown"
estimated_read_time: "10 min"
difficulty: intermediate
tags: [work, wiki, reference, oauth2, api]
---
# OAuth2 Setup Guide
Complete guide for implementing OAuth2...
```
---
## Folder Structure
### Standard Wiki Mirror Structure
```
~/CODEX/03-resources/work/wiki-mirror/
├── _wiki-index.md # Main index
├── engineering/ # Collection folder
│ ├── security/ # Subfolder (hierarchy)
│ │ ├── api-auth-decision.md
│ │ └── security-best-practices.md
│ ├── architecture/
│ │ ├── system-design.md
│ │ └── data-flow.md
│ └── api-docs/
│ ├── oauth2-setup.md
│ ├── token-management.md
│ └── api-reference.md
├── product/
│ ├── design-system.md
│ ├── features/
│ └── user-guides/
└── operations/
├── deployment/
├── monitoring/
└── incident-response/
```
### Project-Specific Wiki Structure
```
~/CODEX/01-projects/work/[project]/
├── _index.md # Project MOC with wiki links
├── notes/
│ ├── requirements.md
│ ├── architecture-notes.md
│ └── implementation-notes.md
├── meetings/
│ └── project-sync-20260128.md
├── decisions/
│ └── tech-stack-decision.md # Also exported to wiki
└── wiki-exports/ # Project-specific wiki copies
├── api-spec.md # Copy from Outline
└── design-decisions.md # Copy from Outline
```
---
## Linking Strategies
### Outline Document Link (MCP URI)
```markdown
# Direct MCP Link (Best for Outline)
[OAuth2 Setup Guide](outline://document/abc123def456)
```
**Pros**:
- Direct integration with Outline MCP
- Always points to current version
- Can open in Outline web UI if MCP fails
**Cons**:
- Requires Outline MCP to be active
- Not clickable in external viewers
### Wiki-Link with Reference
```markdown
# Wiki-Link (Best for Obsidian)
📄 [[OAuth2 Setup Guide]]
```
**Frontmatter link**:
```yaml
---
title: "API Authentication Decision"
wiki_link: "[[OAuth2 Setup Guide]]"
wiki_doc_id: "abc123def456"
---
```
### External URL Link (Fallback)
```markdown
# URL Link (Fallback for offline/viewer access)
[OAuth2 Setup Guide](https://outline.example.com/doc/abc123)
```
**In frontmatter**:
```yaml
---
outline_url: "https://outline.example.com/doc/abc123"
---
```
### Combined Strategy (Recommended)
```markdown
---
title: "API Authentication Decision"
source: outline
document_id: "abc123def456"
wiki_link: "[[OAuth2 Setup Guide]]"
outline_url: "https://outline.example.com/doc/abc123"
tags: [work, decision, api]
---
## Decision
Use OAuth2 for all external APIs.
## References
### Primary Source
📄 [[OAuth2 Setup Guide]](outline://document/abc123)
### Related Documents
📄 [[Token Management Policy]](outline://document/def456)
📄 [[API Security Best Practices]](outline://document/ghi789)
### External Links
- [View in Outline Web UI](https://outline.example.com/doc/abc123)
```
---
## Index Management
### Main Wiki Index
```markdown
---
title: "Outline Wiki Index"
source: outline
last_sync: "2026-01-28T18:50:00Z"
total_docs: 45
total_collections: 6
tags: [work, wiki, outline]
---
# Outline Wiki Index
## Collections
### 📁 Engineering (15 docs)
**ID**: col_eng_123
**Description**: Technical documentation, architecture, APIs
**Subfolders**:
- [security](engineering/security/) (3 docs)
- [architecture](engineering/architecture/) (5 docs)
- [api-docs](engineering/api-docs/) (7 docs)
### 📁 Product (12 docs)
**ID**: col_prod_456
**Description**: Product specs, user guides, features
**Subfolders**:
- [design-system](product/design-system.md) (4 docs)
- [features](product/features/) (6 docs)
- [user-guides](product/user-guides/) (2 docs)
### 📁 Security (8 docs)
**ID**: col_sec_789
**Description**: Security policies, incident response, compliance
### 📁 Operations (10 docs)
**ID**: col_ops_012
**Description**: Deployment, monitoring, runbooks
## Recently Exported
| Date | Document | Collection | Tags |
|-------|-----------|------------|-------|
| 2026-01-28 | OAuth2 Setup Guide | Engineering/Security | api, oauth2 |
| 2026-01-27 | System Design | Engineering/Architecture | architecture |
| 2026-01-26 | Deployment Guide | Operations/Deployment | ops, devops |
## Document Types
- 📄 **Reference**: 30 docs
- 🎯 **Decision**: 8 docs
- 📋 **Process**: 5 docs
- 📘 **Guide**: 2 docs
## Search
- 🔍 [Search Outline for](outline://search/) live content
- 🔍 [Search exports](#exported-documents) in vault
---
## Exported Documents
### By Collection
#### Engineering
- [[OAuth2 Setup Guide]]
- [[Token Management Policy]]
- [[API Security Best Practices]]
- [[System Design]]
- [[Data Flow Architecture]]
#### Product
- [[Design System]]
- [[Component Library]]
- [[User Guide]]
#### Security
- [[Incident Response]]
- [[Security Policy]]
### By Tag
#api
- [[OAuth2 Setup Guide]]
- [[API Security Best Practices]]
#security
- [[API Security Best Practices]]
- [[Incident Response]]
#architecture
- [[System Design]]
- [[Data Flow Architecture]]
```
### Collection-Specific Indexes
Create `_index.md` in each collection folder:
```markdown
---
title: "Engineering Wiki"
collection: Engineering
collection_id: col_eng_123
source: outline
tags: [work, wiki, engineering]
---
# Engineering Wiki
## Overview
Technical documentation, architecture decisions, and API references.
## Structure
### Security (3 docs)
📄 [[API Authentication Decision]]
📄 [[Security Best Practices]]
📄 [[Incident Response]]
### Architecture (5 docs)
📄 [[System Design]]
📄 [[Data Flow]]
📄 [[Component Architecture]]
📄 [[Scalability Guide]]
📄 [[Performance Optimization]]
### API Docs (7 docs)
📄 [[OAuth2 Setup Guide]]
📄 [[Token Management]]
📄 [[API Reference]]
📄 [[Rate Limiting]]
📄 [[Error Handling]]
📄 [[Webhooks]]
📄 [[Testing Guide]]
## Quick Links
- 🔍 [Search Outline](outline://collection/col_eng_123)
- 📄 [Export Collection](outline://export/col_eng_123)
- 🌐 [Open in Web UI](https://outline.example.com/c/col_eng_123)
```
---
## Batch Operations
### Export Multiple Documents
```bash
# Pattern for batch export (manual script outline)
documents = [
{"id": "abc123", "path": "engineering/api/oauth2.md"},
{"id": "def456", "path": "engineering/api/token.md"},
{"id": "ghi789", "path": "engineering/security/best-practices.md"},
]
for doc in documents:
content = export_document(doc["id"])
write_file(f"wiki-mirror/{doc['path']}", content)
update_index(doc["id"], doc["path"])
```
### Update Index After Batch
```markdown
---
title: "Batch Export Report"
export_date: 2026-01-28
documents_exported: 45
collections_exported: 6
---
## Export Summary
- Exported 45 documents from 6 collections
- Total size: 2.3 MB
- Processing time: 3.2 minutes
## Collections Updated
- ✅ Engineering: 15 docs
- ✅ Product: 12 docs
- ✅ Security: 8 docs
- ✅ Operations: 10 docs
## Next Steps
- [ ] Verify all exports in Obsidian
- [ ] Test wiki links
- [ ] Update wiki index
```
---
## Naming Conventions
### File Naming
**Rules**:
1. Lowercase only
2. Replace spaces with hyphens
3. Remove special characters
4. Keep meaningful names
5. Avoid dates in names (use frontmatter instead)
**Examples**:
```
OAuth2 Setup Guide → oauth2-setup-guide.md
API Security Best Practices → api-security-best-practices.md
System Design (2026) → system-design.md (use frontmatter for version)
```
### Folder Naming
**Rules**:
1. Use collection names from Outline
2. Preserve hierarchy (subcollections as subfolders)
3. Consistent with project structure
**Examples**:
```
Engineering/Security → engineering/security/
Engineering/API Docs → engineering/api-docs/
Product/Features → product/features/
```
---
## Version Control for Exports
### Git Tracking
```
~/CODEX/03-resources/work/wiki-mirror/
├── .git/ # Git repo for exports
├── _wiki-index.md
└── engineering/
└── ...
```
**Benefits**:
- Track changes to exported docs
- Diff between export versions
- Revert to previous exports
- Track when docs were last synced
### Sync Workflow
```bash
# Before export
cd ~/CODEX/03-resources/work/wiki-mirror/
git pull
git add .
git commit -m "Pre-export checkpoint"
git push
# After export
git add .
git commit -m "Exported 45 docs from Outline (2026-01-28)"
git push
```
---
## Troubleshooting
### Duplicate Exports
**Problem**: Same document exported multiple times
**Solution**:
1. Check for existing file before export
2. Add timestamp to duplicates: `doc-name.20260128.md`
3. Or ask user: "Overwrite or create new version?"
### Broken Links After Export
**Problem**: Wiki links don't work in Obsidian
**Solution**:
1. Verify document IDs in frontmatter
2. Check file paths match index
3. Use wiki-links for same-vault docs
4. Use MCP URIs for Outline docs
### Large Exports Timeout
**Problem**: Exporting entire collection fails (too large)
**Solution**:
1. Export in batches (e.g., 20 docs at a time)
2. Use `export_collection` instead of individual docs
3. Implement progress tracking
4. Retry failed documents
---
## Best Practices Summary
1. **Always Include Frontmatter**: Document metadata is crucial
2. **Maintain Hierarchy**: Preserve collection structure
3. **Update Index**: Keep wiki index current
4. **Use Multiple Link Types**: MCP URI + wiki-link + URL
5. **Tag Exports**: Make exported docs discoverable
6. **Track Changes**: Use Git for version control
7. **Regular Exports**: Don't wait for job transition
8. **Verify Links**: Test after every export batch
9. **Organize by Type**: Reference, Decision, Process folders
10. **Document Exports**: Keep export log for reference

410
skills/outline/references/outline-workflows.md
View File

@@ -1,410 +0,0 @@
# Outline Workflows
This reference provides detailed examples and patterns for Outline wiki integration with Obsidian.
## Table of Contents
1. [Export Decision to Wiki](#export-decision-to-wiki)
2. [Project Documentation Sync](#project-documentation-sync)
3. [Knowledge Discovery](#knowledge-discovery)
4. [Batch Export](#batch-export)
5. [Wiki Migration](#wiki-migration)
---
## Export Decision to Wiki
### Scenario
After a meeting, you made an important decision about API authentication. You want to preserve it in the company wiki.
### Workflow
```
User: "Export decision: Use OAuth2 for all external APIs"
Outline skill:
1. Create document:
- Title: "API Authentication Decision"
- Collection: Engineering/Security
- Content:
---
title: "API Authentication Decision"
date: 2026-01-28
decision_made_by: "[Team Name]"
tags: [decision, api, security]
---
# Decision
Use OAuth2 for all external API integrations.
# Reasoning
- OAuth2 provides better security (no shared secrets)
- Token rotation reduces risk exposure
- Industry standard for API auth
- Existing libraries available
# Implementation
- Use RFC 6749 OAuth2 framework
- Implement refresh token flow
- Set 30-day token expiry
- Document API endpoints in collection
# Alternatives Considered
- API Keys: Rejected (security risk)
- JWT: Rejected (overkill for external APIs)
- Custom Auth: Rejected (maintenance burden)
# Related Documents
- [[OAuth2 Setup Guide]]
- [[Token Management Policy]]
- [[API Security Best Practices]]
2. Confirm: "Created API Authentication Decision in Engineering/Security"
3. Offer: "Link to project?"
```
### Obsidian Integration
After creating in Outline, create cross-reference in Obsidian:
```markdown
~/CODEX/01-projects/work/[project]/decisions/api-auth-decision.md
---
title: "API Authentication Decision"
date: 2026-01-28
source: outline
outline_doc_id: [ID]
tags: [work, decision, api]
---
## Decision
Use OAuth2 for all external API integrations.
## Outline Link
📄 [API Authentication Decision](outline://document/abc123)
## Context
- Made during API integration project
- Discussed in [Security Review Meeting]
- Approved by: [Stakeholder names]
## Project Notes
- Update authentication service by Q2
- Train team on OAuth2 flow
```
---
## Project Documentation Sync
### Scenario
You're starting a new project. You want to link project docs with the wiki for context.
### Workflow
```
User: "Start project: Customer Portal Redesign"
outline skill:
1. Search for related docs:
- "Search Outline for Customer Portal"
- "Search Outline for UI/UX guidelines"
- "Search Outline for architecture decisions"
2. Present findings:
📄 Customer Portal Architecture (Engineering)
📄 UI Design System (Product/Design)
📄 Accessibility Guidelines (Engineering/Docs)
3. Create project folder in Obsidian with wiki links
```
### Project MOC with Wiki Links
```markdown
~/CODEX/01-projects/work/customer-portal-redesign/_index.md
---
title: "Customer Portal Redesign"
status: active
deadline: 2026-06-30
priority: high
tags: [work, project]
---
## Overview
Redesign of customer portal with improved UX, performance, and accessibility.
## Wiki Resources
### Architecture
📄 [[Customer Portal Architecture]](outline://document/abc123)
- Backend architecture decisions
- Database schema
- API endpoints
### Design System
📄 [[UI Design System]](outline://document/def456)
- Component library
- Color palette
- Typography
### Guidelines
📄 [[Accessibility Guidelines]](outline://document/ghi789)
- WCAG 2.1 AA compliance
- Testing checklist
- Common patterns
## Notes
<!-- Your project notes here -->
## Tasks
<!-- Tasks linked from Basecamp -->
```
---
## Knowledge Discovery
### Scenario
You need to implement a feature but don't remember the authentication pattern used in the codebase.
### Workflow
```
User: "Ask Outline: How do we handle API authentication?"
outline skill:
1. ask_ai_about_documents(
question: "How do we handle API authentication?"
collection_id: "engineering"
)
2. Present AI answer with sources:
🤖 **Answer**:
Based on 12 documents, here's the authentication pattern:
**Standard Pattern**:
- OAuth2 with refresh tokens
- 30-day token expiry
- Automatic refresh before expiry
**Implementation**:
1. Use `/auth/oauth2/token` endpoint
2. Store refresh token securely
3. Implement token rotation
4. Handle 401 Unauthorized with retry
**Exceptions**:
- Internal services use API keys (documented separately)
- Admin portals use session-based auth
**Key Sources**:
1. [[OAuth2 Setup Guide]](outline://document/abc123)
2. [[Token Management Policy]](outline://document/def456)
3. [[API Security Best Practices]](outline://document/ghi789)
3. Offer:
- "Read OAuth2 Setup Guide?"
- "Export to current project?"
```
---
## Batch Export
### Scenario
You're preparing for a job transition or need offline access to critical documentation.
### Workflow
```
User: "Export all Engineering docs to Obsidian"
outline skill:
1. export_collection(collection_id: "engineering_id")
2. Create Obsidian structure:
~/CODEX/03-resources/work/wiki-mirror/engineering/
├── api-docs/
│ ├── oauth2-setup-guide.md
│ ├── token-management.md
│ └── api-security.md
├── architecture/
│ ├── system-design.md
│ └── data-flow.md
└── decisions/
├── auth-decision.md
└── database-choice.md
3. Update wiki index:
Update ~/CODEX/03-resources/work/wiki-mirror/_wiki-index.md
with new export metadata
4. Confirm: "Exported 15 Engineering docs to wiki-mirror/engineering/"
```
---
## Wiki Migration
### Scenario
You're switching from a different wiki system to Outline and want to migrate content.
### Workflow (No n8n - Manual Process)
```
Step 1: Export from Old Wiki
- Export all pages as Markdown
- Preserve structure/folders
- Keep metadata (created dates, authors)
Step 2: Batch Import to Outline
outline skill:
1. batch_create_documents(documents):
[
{
"title": "API Documentation",
"collection_id": "engineering_id",
"text": "# API Documentation\n\n...",
"publish": true
},
{
"title": "System Design",
"collection_id": "engineering_id",
"text": "# System Design\n\n...",
"publish": true
}
]
2. Confirm: "Imported 50 documents to Outline"
Step 3: Verify Migration
- Check Outline web UI
- Verify document counts
- Test search functionality
- Fix any formatting issues
Step 4: Archive Old Wiki
- Mark old wiki as read-only
- Add deprecation notice
- Link to new Outline location
```
---
## Cross-Tool Patterns
### Outline ↔ Obsidian
| When | Action | Location |
|------|---------|----------|
| Important decision | Create in Outline + link in Obsidian | Outline: Primary, Obsidian: Reference |
| Project docs | Link wiki docs from project MOC | Obsidian: Primary, Outline: Source |
| Meeting outcome | Export key decisions to Outline | Outline: Persistent, Obsidian: Session context |
| Research | Export findings to Outline | Outline: Knowledge base, Obsidian: Working notes |
### Search Workflow
1. **First**: Search Obsidian vault (personal knowledge)
2. **Then**: Search Outline wiki (team knowledge)
3. **Finally**: Search both with context
```
User: "Find info about OAuth2"
Obsidian search:
- Check ~/CODEX/03-resources/work/wiki-mirror/
- Check project notes
- Return local copies
Outline search:
- search_documents("OAuth2")
- Return live wiki content
- Export if needed for offline access
```
---
## Advanced Workflows
### Decision Audit
Periodically review all decisions to check:
- Relevance (still applicable?)
- Implementation status (actually done?)
- Outdated decisions (need update?)
```bash
# List all decision docs
search_documents("decision")
# For each:
read_document(document_id)
# Check frontmatter:
# - implemented: true/false
# - reviewed_at: date
# - status: active/archived
```
### Knowledge Gap Analysis
Identify missing documentation:
1. List all project areas
2. Search Outline for each area
3. Identify gaps:
- "No results found for X"
- "Documentation is outdated"
- "Information is scattered"
Create follow-up tasks:
```markdown
## Documentation Tasks
- [ ] Write API rate limiting guide (missing)
- [ ] Update OAuth2 examples (outdated)
- [ ] Create testing best practices (scattered)
```
---
## Troubleshooting
### Export Failed
**Problem**: Document exported to wrong location or failed to export
**Solution**:
1. Verify collection hierarchy
2. Check Obsidian vault path
3. Ensure directory exists: `mkdir -p 03-resources/work/wiki-mirror/[collection]/`
4. Check file permissions
### Search No Results
**Problem**: search_documents returns empty results
**Solution**:
1. Try broader query (fewer keywords)
2. Remove collection_id to search everywhere
3. Check if document exists in Outline web UI
4. Use ask_ai_about_documents for semantic search
### Wiki Link Broken
**Problem**: `(outline://document/abc123)` link doesn't work
**Solution**:
1. Verify document_id is correct
2. Check Outline MCP is running
3. Test with `read_document(document_id)`
4. Fallback: Use Outline web UI URL
---
## Best Practices Summary
1. **Export Early, Export Often**: Don't wait until job transition
2. **Link Immediately**: Create Obsidian links when exporting
3. **Index Everything**: Maintain wiki index for easy navigation
4. **AI as Helper**: Use `ask_ai_about_documents` but verify sources
5. **Preserve Hierarchy**: Maintain collection structure in exports
6. **Tag Generously**: Add tags for discoverability
7. **Cross-Reference**: Link related documents in Outline
8. **Decisions Matter**: Export all decisions, not just docs
---
## Automation (Future n8n Workflows)
These will be implemented later with n8n automation:
1. **Daily Wiki Sync**: Export updated Outline docs each night
2. **Decision Auto-Export**: Hook meeting-notes → Outline create
3. **Search Integration**: Combine Obsidian + Outline search
4. **Backup Workflow**: Weekly export_all_collections

172
skills/outlook/SKILL.md
View File

@@ -1,172 +0,0 @@
---
name: outlook
description: "Outlook Graph API email integration via MCP. Use when: (1) Reading or sending emails, (2) Managing inbox folders and organization, (3) Working with calendar events, (4) Managing contacts, (5) Searching mail content, (6) Managing email rules and filters. Triggers: 'email', 'Outlook', 'inbox', 'calendar', 'contacts', 'folder', 'mail', 'message'."
compatibility: opencode
---
# Outlook Graph API Integration
Integration with Microsoft Outlook via Graph API through MCP. Provides comprehensive access to email, calendar, contacts, and folder management.
## Core Operations
### Mail Access
**List messages**: `list_messages(folder_id=None, top=25, skip=0)` - Returns messages from a folder. Use `folder_id` to target specific folders (defaults to Inbox).
**Get message**: `get_message(message_id)` - Full message details including body, headers, and attachments.
**Get message content**: `get_message_content(message_id)` - Retrieve message body (HTML/Text).
**List attachments**: `list_attachments(message_id)` - All attachments for a message.
**Get attachment**: `get_attachment(message_id, attachment_id)` - Download attachment content.
### Mail CRUD
**Create draft**: `create_draft(subject, body, to_recipients, cc_recipients=None, bcc_recipients=None, importance=None, is_html=True)` - Create email draft.
**Send email**: `send_email(subject, body, to_recipients, cc_recipients=None, bcc_recipients=None, importance=None, is_html=True)` - Send email directly.
**Send draft**: `send_draft(message_id)` - Send an existing draft.
**Reply to email**: `reply_to_message(message_id, body, is_html=True)` - Reply to sender.
**Reply all**: `reply_all_message(message_id, body, is_html=True)` - Reply to sender and all recipients.
**Forward email**: `forward_message(message_id, to_recipients, body=None, is_html=True)` - Forward message to new recipients.
**Update message**: `update_message(message_id, subject=None, body=None, importance=None, is_read=None)` - Update message properties.
**Delete message**: `delete_message(message_id)` - Move to deleted items.
**Delete permanently**: `delete_message_permanently(message_id)` - Permanently remove message.
### Folder Management
**List folders**: `list_folders()` - All accessible folders including custom ones.
**Get folder**: `get_folder(folder_id)` - Folder details and metadata.
**Create folder**: `create_folder(name, parent_folder_id=None)` - Create new folder.
**Update folder**: `update_folder(folder_id, name=None)` - Rename folder.
**Delete folder**: `delete_folder(folder_id)` - Remove folder and all contents.
**Move messages**: `move_messages(message_ids, destination_folder_id)` - Move messages between folders.
**Copy messages**: `copy_messages(message_ids, destination_folder_id)` - Copy messages to another folder.
### Calendar Events
**List events**: `list_events(calendar_id=None, top=25, skip=0)` - Events from calendar (defaults to primary calendar).
**Get event**: `get_event(event_id)` - Full event details including attendees and location.
**Create event**: `create_event(subject, start_time, end_time, body=None, location=None, attendees=None, is_all_day=False)` - Create calendar event.
**Update event**: `update_event(event_id, subject=None, start_time=None, end_time=None, body=None, location=None, attendees=None)` - Modify event.
**Delete event**: `delete_event(event_id)` - Remove event.
**Accept event**: `accept_event(event_id, response_comment=None, send_response=True)` - Accept meeting invitation.
**Decline event**: `decline_event(event_id, response_comment=None, send_response=True)` - Decline meeting invitation.
**Tentatively accept**: `tentatively_accept_event(event_id, response_comment=None, send_response=True)` - Tentatively accept invitation.
**List calendars**: `list_calendars()` - All user calendars.
### Contacts
**List contacts**: `list_contacts(folder_id=None, top=25, skip=0)` - Contacts from folder (defaults to default contacts folder).
**Get contact**: `get_contact(contact_id)` - Full contact details.
**Create contact**: `create_contact(given_name, surname, email_addresses, phone_numbers=None, business_address=None)` - Create new contact.
**Update contact**: `update_contact(contact_id, given_name=None, surname=None, email_addresses=None, phone_numbers=None, business_address=None)` - Modify contact.
**Delete contact**: `delete_contact(contact_id)` - Remove contact.
**List contact folders**: `list_contact_folders()` - All contact folders.
**Create contact folder**: `create_contact_folder(name)` - Create new contact folder.
### Search
**Search mail**: `search_mail(query, folder_id=None, top=25)` - Search emails by content across folders.
**Search contacts**: `search_contacts(query)` - Search contacts by name, email, or other properties.
**Search events**: `search_events(query)` - Search calendar events by subject or location.
## Common Workflows
### Send an email
1. Compose email: `send_email("Subject", "Body content", ["recipient@example.com"])`
2. For complex emails with attachments, use `create_draft()` first, then `send_draft()`
### Organize inbox
1. List folders: `list_folders()` to see available folders
2. Create new folder: `create_folder("Project Alpha")`
3. Move messages: `move_messages(["msg-id-1", "msg-id-2"], "new-folder-id")`
### Process meeting invitation
1. Check invitation: `get_message(message_id)` to view details
2. Accept: `accept_event(event_id, response_comment="I'll attend")`
3. Or decline: `decline_event(event_id, response_comment="Cannot make it")`
### Search for old emails
1. Use `search_mail("project deadline", top=50)` for broad search
2. Use `list_messages(folder_id="sent-items")` to check sent folder
3. Combine with filters: `search_mail("report", folder_id="archive")`
### Create recurring meeting
1. Use `create_event()` with appropriate `start_time` and `end_time`
2. Set up multiple events or use calendar-specific recurrence features
### Manage project correspondence
1. Create project folder: `create_folder("Q4 Project")`
2. Search for related emails: `search_mail("Q4 Project")`
3. Move relevant emails: `move_messages(message_ids, "project-folder-id")`
4. Track contacts: `create_contact("John", "Doe", ["john@partner.com"])`
## IDs and Discovery
Outlook Graph API uses resource IDs. When operations require IDs:
1. **Messages**: Start with `list_messages()` to get message IDs
2. **Folders**: Use `list_folders()` to discover folder IDs
3. **Events**: Use `list_events()` to get event IDs
4. **Contacts**: Use `list_contacts()` to get contact IDs
Most IDs are returned in list operations and can be used directly in CRUD operations.
## Important Notes
**Email body format**: The `is_html` parameter controls whether email body is HTML (default) or plain text. HTML provides rich formatting but plain text is more universal.
**Recipients format**: Email addresses should be provided as arrays of strings: `["user1@example.com", "user2@example.com"]`.
**Date/time format**: All datetime values should be in ISO 8601 format (e.g., `2024-12-25T14:30:00`).
**Batch operations**: Some operations like `move_messages()` and `copy_messages()` accept arrays of IDs for batch processing.
**Pagination**: List operations support `top` (max results) and `skip` (offset) parameters for handling large datasets.
**Folder IDs**: Common folder IDs include:
- Inbox (default for most operations)
- Sent Items
- Drafts
- Deleted Items
- Archive
Use `list_folders()` to get exact IDs and discover custom folders.

165
skills/plan-writing/SKILL.md
View File

@@ -1,165 +0,0 @@
---
name: plan-writing
description: "Transform ideas into comprehensive, actionable project plans with templates. Use when: (1) creating project kickoff documents, (2) structuring new projects, (3) building detailed task breakdowns, (4) documenting project scope and stakeholders, (5) setting up project for execution. Triggers: project plan, kickoff document, plan out, structure project, project setup, create plan for, what do I need to start."
compatibility: opencode
---
# Plan Writing
Transform brainstormed ideas into comprehensive, actionable project plans using modular templates.
## Quick Reference
| Project Type | Templates to Use |
|--------------|------------------|
| Solo, <2 weeks | project-brief, todo-structure |
| Solo, >2 weeks | project-brief, todo-structure, risk-register |
| Team, any size | project-kickoff, stakeholder-map, todo-structure, risk-register |
## Process
### 1. Intake
Gather initial context:
- What project are we planning?
- Check for existing brainstorming output in `docs/brainstorms/`
- If starting fresh, gather basic context first
### 2. Scope Assessment
Ask these questions (one at a time):
1. **Solo or team project?**
- Solo → lighter documentation
- Team → need alignment docs (kickoff, stakeholders)
2. **Rough duration estimate?**
- <2 weeks → skip risk register
- >2 weeks → include risk planning
3. **Known deadline or flexible?**
- Hard deadline → prioritize milestone planning
- Flexible → focus on phased approach
4. **Which PARA area does this belong to?** (optional)
- Helps categorization and later task-management integration
### 3. Component Selection
Based on scope, select appropriate templates:
```
"Based on [team project, 6 weeks], I'll include:
✓ Project Kickoff (team alignment)
✓ Stakeholder Map (communication planning)
✓ Todo Structure (task breakdown)
✓ Risk Register (duration >2 weeks)
Shall I proceed with this structure?"
```
See [references/component-guide.md](references/component-guide.md) for selection logic.
### 4. Draft Generation
For each selected template:
1. Load template from `assets/templates/`
2. Fill with project-specific content
3. Present each major section for validation
4. Adjust based on feedback
Work through templates in this order:
1. Kickoff/Brief (establishes context)
2. Stakeholders (who's involved)
3. Todos (what needs doing)
4. Risks (what could go wrong)
### 5. Output
Generate final documents:
- Create `docs/plans/<project-name>/` directory
- Write each component as separate file
- Create `index.md` linking all components
```
docs/plans/<project-name>/
├── index.md # Links to all components
├── kickoff.md # or brief.md for solo projects
├── stakeholders.md # if team project
├── tasks.md # task breakdown
├── risks.md # if >2 weeks duration
└── updates/ # for future progress updates
└── YYYY-MM-DD.md
```
### 6. Handoff (Optional)
After plan is complete, offer next steps:
> "Ready to create this project in Basecamp? I can:
> - Create todo lists from the task structure
> - Set up card table columns from phases
> - Add initial cards/todos with due dates"
This triggers the basecamp skill for execution.
## Templates
All templates in `assets/templates/`:
| Template | Purpose | When to Include |
|----------|---------|-----------------|
| project-kickoff.md | Comprehensive 8-section kickoff | Team projects |
| project-brief.md | 1-page summary | Solo or simple projects |
| stakeholder-map.md | Who needs what, when | Team projects |
| risk-register.md | Risks and mitigations | Projects >2 weeks |
| todo-structure.md | Hierarchical task breakdown | Always |
| progress-update.md | Status update template | For ongoing tracking |
## PARA Integration (Optional)
If user wants PARA integration:
1. Prompt for Area assignment (from their defined Areas)
2. Can trigger task-management skill to create Obsidian task entries
3. Include Area reference in kickoff/brief document
This is optional - not all users use PARA.
## Integration with Other Skills
| From | To plan-writing | Output |
|------|-----------------|--------|
| brainstorming | Decision/context | Informs kickoff scope |
| plan-writing | → basecamp | Todo lists, cards |
| plan-writing | → task-management | Obsidian tasks (optional) |
## Example Workflow
```
User: "Create a project plan for launching the Q2 training program"
AI: "I'll help structure this project. First, a few questions:
Is this a solo project or will others be involved?"
User: "Team - 3 people"
AI: "Duration estimate?
a) Less than 2 weeks
b) 2-4 weeks
c) More than a month"
User: "B - about 3 weeks"
AI: "Got it. For a 3-week team project, I'll include:
✓ Project Kickoff (team alignment)
✓ Stakeholder Map (communication)
✓ Todo Structure (task breakdown)
✓ Risk Register (3 weeks warrants this)
Shall I proceed?"
User: "Yes"
AI: [Proceeds through each template, filling with project details]
```

89
skills/plan-writing/assets/templates/progress-update.md
View File

@@ -1,89 +0,0 @@
# Progress Update: [Project Name]
**Period**: [Date] to [Date]
**Author**: [Name]
**Status**: 🟢 On Track / 🟡 At Risk / 🔴 Blocked
---
## Summary
[2-3 sentence executive summary: Where are we, what's the headline?]
**Overall Progress**: [X]% complete
---
## Completed This Period
- [x] [Task/milestone completed] - [Impact or note]
- [x] [Task completed]
- [x] [Task completed]
**Highlights**:
- [Notable achievement or win]
---
## In Progress
| Task | Owner | Progress | Expected Complete |
|------|-------|----------|-------------------|
| [Task 1] | [Name] | [X]% | [Date] |
| [Task 2] | [Name] | [X]% | [Date] |
| [Task 3] | [Name] | [X]% | [Date] |
---
## Blockers & Risks
### Active Blockers
| Blocker | Impact | Owner | Action Needed | ETA |
|---------|--------|-------|---------------|-----|
| [Blocker 1] | [High/Med/Low] | [Name] | [What's needed] | [Date] |
### Emerging Risks
| Risk | Probability | Mitigation |
|------|-------------|------------|
| [Risk 1] | [H/M/L] | [Action] |
---
## Next Period Plan
**Focus**: [Main focus for next period]
| Priority | Task | Owner | Target Date |
|----------|------|-------|-------------|
| 1 | [Highest priority task] | [Name] | [Date] |
| 2 | [Second priority] | [Name] | [Date] |
| 3 | [Third priority] | [Name] | [Date] |
---
## Metrics
| Metric | Target | Current | Trend |
|--------|--------|---------|-------|
| [Metric 1] | [X] | [Y] | ↑/↓/→ |
| [Metric 2] | [X] | [Y] | ↑/↓/→ |
| Tasks Complete | [X] | [Y] | ↑ |
---
## Decisions Needed
- [ ] [Decision 1]: [Options and recommendation] - Need by: [Date]
- [ ] [Decision 2]: [Context] - Need by: [Date]
---
## Notes / Context
[Any additional context, changes in scope, stakeholder feedback, etc.]
---
*Next update: [Date]*

48
skills/plan-writing/assets/templates/project-brief.md
View File

@@ -1,48 +0,0 @@
# Project Brief: [Project Name]
**Owner**: [Name]
**Timeline**: [Start Date] → [Target Date]
**Area**: [PARA Area, if applicable]
## Goal
[One clear sentence: What will be true when this project is complete?]
## Success Criteria
How we'll know it's done:
- [ ] [Criterion 1 - specific and measurable]
- [ ] [Criterion 2]
- [ ] [Criterion 3]
## Scope
**Included**:
- [Deliverable 1]
- [Deliverable 2]
**Not Included**:
- [Exclusion 1]
## Key Milestones
| Milestone | Target Date | Status |
|-----------|-------------|--------|
| [Milestone 1] | [Date] | [ ] |
| [Milestone 2] | [Date] | [ ] |
| [Complete] | [Date] | [ ] |
## Initial Tasks
1. [ ] [First task to start] - Due: [Date]
2. [ ] [Second task]
3. [ ] [Third task]
## Notes
[Any context, constraints, or references worth capturing]
---
*Created: [Date]*

106
skills/plan-writing/assets/templates/project-kickoff.md
View File

@@ -1,106 +0,0 @@
# Project Kickoff: [Project Name]
## 1. Project Essentials
| Field | Value |
|-------|-------|
| **Project Name** | [Name] |
| **Owner** | [Name] |
| **Start Date** | [YYYY-MM-DD] |
| **Target Completion** | [YYYY-MM-DD] |
| **PARA Area** | [Area, if applicable] |
### Overview
[2-3 sentence description of what this project will accomplish and why it matters.]
## 2. Goals and Success Criteria
**Primary Goal**: [One sentence describing the end state - what does "done" look like?]
**Success Criteria**:
- [ ] [Measurable criterion 1]
- [ ] [Measurable criterion 2]
- [ ] [Measurable criterion 3]
**Out of Scope** (explicitly):
- [Item that might be assumed but is NOT included]
- [Another exclusion]
## 3. Stakeholders
| Role | Person | Involvement Level |
|------|--------|-------------------|
| Project Owner | [Name] | High - decisions |
| Core Team | [Names] | High - execution |
| Informed | [Names] | Low - updates only |
| Approver | [Name, if any] | Medium - sign-off |
## 4. Timeline and Milestones
| Milestone | Target Date | Dependencies | Owner |
|-----------|-------------|--------------|-------|
| [Milestone 1] | [Date] | None | [Who] |
| [Milestone 2] | [Date] | Milestone 1 | [Who] |
| [Milestone 3] | [Date] | Milestone 2 | [Who] |
| **Project Complete** | [Date] | All above | [Owner] |
### Key Dates
- **Kickoff**: [Date]
- **First Review**: [Date]
- **Final Deadline**: [Date]
## 5. Scope
### In Scope
- [Deliverable 1]: [Brief description]
- [Deliverable 2]: [Brief description]
- [Deliverable 3]: [Brief description]
### Out of Scope
- [Explicitly excluded item 1]
- [Explicitly excluded item 2]
### Assumptions
- [Assumption 1 - e.g., "Budget approved"]
- [Assumption 2 - e.g., "Team available full-time"]
## 6. Risks
| Risk | Probability | Impact | Mitigation | Owner |
|------|-------------|--------|------------|-------|
| [Risk 1] | H/M/L | H/M/L | [Plan] | [Who] |
| [Risk 2] | H/M/L | H/M/L | [Plan] | [Who] |
*See detailed risk register if needed: [link to risks.md]*
## 7. Communication Plan
| What | Audience | Frequency | Channel | Owner |
|------|----------|-----------|---------|-------|
| Status Update | All stakeholders | Weekly | [Email/Basecamp] | [Who] |
| Team Sync | Core team | [Daily/2x week] | [Meeting/Slack] | [Who] |
| Milestone Review | Approvers | At milestone | [Meeting] | [Who] |
### Escalation Path
1. First: [Team lead/Owner]
2. Then: [Manager/Sponsor]
3. Finally: [Executive, if applicable]
## 8. Next Steps
Immediate actions to kick off the project:
- [ ] [Action 1] - @[owner] - Due: [date]
- [ ] [Action 2] - @[owner] - Due: [date]
- [ ] [Action 3] - @[owner] - Due: [date]
---
*Document created: [Date]*
*Last updated: [Date]*

104
skills/plan-writing/assets/templates/risk-register.md
View File

@@ -1,104 +0,0 @@
# Risk Register: [Project Name]
## Risk Summary
| ID | Risk | Probability | Impact | Risk Score | Status |
|----|------|-------------|--------|------------|--------|
| R1 | [Brief risk name] | H/M/L | H/M/L | [H/M/L] | Open |
| R2 | [Brief risk name] | H/M/L | H/M/L | [H/M/L] | Open |
| R3 | [Brief risk name] | H/M/L | H/M/L | [H/M/L] | Open |
**Risk Score**: Probability × Impact (H×H=Critical, H×M or M×H=High, M×M=Medium, others=Low)
---
## Detailed Risk Analysis
### R1: [Risk Name]
| Aspect | Detail |
|--------|--------|
| **Description** | [What could go wrong?] |
| **Probability** | High / Medium / Low |
| **Impact** | High / Medium / Low |
| **Category** | Technical / Resource / External / Schedule / Budget |
| **Trigger** | [What would indicate this risk is materializing?] |
**Mitigation Plan**:
- [Action 1 to reduce probability or impact]
- [Action 2]
**Contingency Plan** (if risk occurs):
- [Fallback action 1]
- [Fallback action 2]
**Owner**: [Name]
**Review Date**: [Date]
---
### R2: [Risk Name]
| Aspect | Detail |
|--------|--------|
| **Description** | [What could go wrong?] |
| **Probability** | High / Medium / Low |
| **Impact** | High / Medium / Low |
| **Category** | Technical / Resource / External / Schedule / Budget |
| **Trigger** | [What would indicate this risk is materializing?] |
**Mitigation Plan**:
- [Action 1]
- [Action 2]
**Contingency Plan**:
- [Fallback action]
**Owner**: [Name]
**Review Date**: [Date]
---
### R3: [Risk Name]
| Aspect | Detail |
|--------|--------|
| **Description** | [What could go wrong?] |
| **Probability** | High / Medium / Low |
| **Impact** | High / Medium / Low |
| **Category** | Technical / Resource / External / Schedule / Budget |
| **Trigger** | [What would indicate this risk is materializing?] |
**Mitigation Plan**:
- [Action 1]
- [Action 2]
**Contingency Plan**:
- [Fallback action]
**Owner**: [Name]
**Review Date**: [Date]
---
## Risk Categories
| Category | Examples |
|----------|----------|
| **Technical** | Technology doesn't work, integration issues, performance |
| **Resource** | Key person unavailable, skill gaps, overcommitment |
| **External** | Vendor delays, regulatory changes, dependencies |
| **Schedule** | Delays, unrealistic timeline, competing priorities |
| **Budget** | Cost overruns, funding cuts, unexpected expenses |
## Review Schedule
- **Weekly**: Quick scan of high risks
- **Bi-weekly**: Full risk register review
- **At milestones**: Comprehensive reassessment
---
*Created: [Date]*
*Last reviewed: [Date]*
*Next review: [Date]*

72
skills/plan-writing/assets/templates/stakeholder-map.md
View File

@@ -1,72 +0,0 @@
# Stakeholder Map: [Project Name]
## Stakeholder Matrix
| Stakeholder | Role | Interest Level | Influence | Information Needs |
|-------------|------|----------------|-----------|-------------------|
| [Name/Group] | [Role] | High/Medium/Low | High/Medium/Low | [What they need to know] |
| [Name/Group] | [Role] | High/Medium/Low | High/Medium/Low | [What they need to know] |
| [Name/Group] | [Role] | High/Medium/Low | High/Medium/Low | [What they need to know] |
## Communication Plan by Stakeholder
### [Stakeholder 1: Name/Role]
| Aspect | Detail |
|--------|--------|
| **Needs** | [What information they need] |
| **Frequency** | [How often: daily, weekly, at milestones] |
| **Channel** | [Email, Basecamp, meeting, Slack] |
| **Format** | [Brief update, detailed report, presentation] |
| **Owner** | [Who communicates with them] |
### [Stakeholder 2: Name/Role]
| Aspect | Detail |
|--------|--------|
| **Needs** | [What information they need] |
| **Frequency** | [How often] |
| **Channel** | [Preferred channel] |
| **Format** | [Format preference] |
| **Owner** | [Who communicates] |
### [Stakeholder 3: Name/Role]
| Aspect | Detail |
|--------|--------|
| **Needs** | [What information they need] |
| **Frequency** | [How often] |
| **Channel** | [Preferred channel] |
| **Format** | [Format preference] |
| **Owner** | [Who communicates] |
## RACI Matrix
| Decision/Task | [Person 1] | [Person 2] | [Person 3] | [Person 4] |
|---------------|------------|------------|------------|------------|
| [Decision 1] | R | A | C | I |
| [Decision 2] | I | R | A | C |
| [Task 1] | R | I | I | A |
**Legend**:
- **R** = Responsible (does the work)
- **A** = Accountable (final decision maker)
- **C** = Consulted (input required)
- **I** = Informed (kept updated)
## Escalation Path
1. **First Level**: [Name/Role] - for [types of issues]
2. **Second Level**: [Name/Role] - if unresolved in [timeframe]
3. **Executive**: [Name/Role] - for [critical blockers only]
## Notes
- [Any stakeholder-specific considerations]
- [Political or relationship notes]
- [Historical context if relevant]
---
*Created: [Date]*
*Last updated: [Date]*

94
skills/plan-writing/assets/templates/todo-structure.md
View File

@@ -1,94 +0,0 @@
# Task Structure: [Project Name]
## Overview
| Metric | Value |
|--------|-------|
| **Total Tasks** | [X] |
| **Phases** | [Y] |
| **Timeline** | [Start] → [End] |
---
## Phase 1: [Phase Name]
**Target**: [Date]
**Owner**: [Name]
| # | Task | Owner | Estimate | Due | Depends On | Status |
|---|------|-------|----------|-----|------------|--------|
| 1.1 | [Task description] | [Name] | [Xh/Xd] | [Date] | - | [ ] |
| 1.2 | [Task description] | [Name] | [Xh/Xd] | [Date] | 1.1 | [ ] |
| 1.3 | [Task description] | [Name] | [Xh/Xd] | [Date] | - | [ ] |
**Phase Deliverable**: [What's complete when this phase is done]
---
## Phase 2: [Phase Name]
**Target**: [Date]
**Owner**: [Name]
| # | Task | Owner | Estimate | Due | Depends On | Status |
|---|------|-------|----------|-----|------------|--------|
| 2.1 | [Task description] | [Name] | [Xh/Xd] | [Date] | Phase 1 | [ ] |
| 2.2 | [Task description] | [Name] | [Xh/Xd] | [Date] | 2.1 | [ ] |
| 2.3 | [Task description] | [Name] | [Xh/Xd] | [Date] | - | [ ] |
**Phase Deliverable**: [What's complete when this phase is done]
---
## Phase 3: [Phase Name]
**Target**: [Date]
**Owner**: [Name]
| # | Task | Owner | Estimate | Due | Depends On | Status |
|---|------|-------|----------|-----|------------|--------|
| 3.1 | [Task description] | [Name] | [Xh/Xd] | [Date] | Phase 2 | [ ] |
| 3.2 | [Task description] | [Name] | [Xh/Xd] | [Date] | 3.1 | [ ] |
| 3.3 | [Task description] | [Name] | [Xh/Xd] | [Date] | 3.1 | [ ] |
**Phase Deliverable**: [What's complete when this phase is done]
---
## Unphased / Ongoing Tasks
| # | Task | Owner | Frequency | Notes |
|---|------|-------|-----------|-------|
| O.1 | [Recurring task] | [Name] | Weekly | [Notes] |
| O.2 | [Monitoring task] | [Name] | Daily | [Notes] |
---
## Dependencies Summary
```
Phase 1 ──────► Phase 2 ──────► Phase 3
│ │
├── 1.1 ► 1.2 ├── 2.1 ► 2.2
└── 1.3 └── 2.3 (parallel)
```
## Milestone Checklist
- [ ] **Milestone 1**: [Name] - [Date]
- [ ] [Required task 1.1]
- [ ] [Required task 1.2]
- [ ] **Milestone 2**: [Name] - [Date]
- [ ] [Required task 2.1]
- [ ] [Required task 2.2]
- [ ] **Project Complete** - [Date]
- [ ] All phases complete
- [ ] Success criteria met
- [ ] Handoff complete
---
*Created: [Date]*
*Last updated: [Date]*

117
skills/plan-writing/references/component-guide.md
View File

@@ -1,117 +0,0 @@
# Component Selection Guide
Decision matrix for which templates to include based on project characteristics.
## Decision Matrix
| Question | If Yes | If No |
|----------|--------|-------|
| Team project (>1 person)? | +kickoff, +stakeholders | Use brief instead of kickoff |
| Duration >2 weeks? | +risk-register | Skip risks |
| External stakeholders? | +stakeholders (detailed) | Stakeholders optional |
| Complex dependencies? | +detailed todos with deps | Simple todo list |
| Ongoing tracking needed? | +progress-update template | One-time plan |
## Quick Selection by Project Type
### Solo, Short (<2 weeks)
```
✓ project-brief.md
✓ todo-structure.md
```
### Solo, Medium (2-4 weeks)
```
✓ project-brief.md
✓ todo-structure.md
✓ risk-register.md
```
### Solo, Long (>4 weeks)
```
✓ project-brief.md (or kickoff for complex)
✓ todo-structure.md
✓ risk-register.md
✓ progress-update.md (for self-tracking)
```
### Team, Any Duration
```
✓ project-kickoff.md (always for team alignment)
✓ stakeholder-map.md
✓ todo-structure.md
✓ risk-register.md (if >2 weeks)
✓ progress-update.md (for status updates)
```
## Template Purposes
### project-kickoff.md
Full 8-section document for team alignment:
1. Project essentials (name, owner, dates)
2. Goals and success criteria
3. Stakeholders overview
4. Timeline and milestones
5. Scope (in/out)
6. Risks overview
7. Communication plan
8. Next steps
**Use when**: Multiple people need alignment on what/why/how.
### project-brief.md
1-page summary for simpler projects:
- Goal statement
- Success criteria
- Key milestones
- Initial tasks
**Use when**: Solo project or simple scope that doesn't need formal kickoff.
### stakeholder-map.md
Communication matrix:
- Who needs information
- What they need to know
- How often
- Which channel
**Use when**: Team projects with multiple stakeholders needing different information.
### risk-register.md
Risk tracking table:
- Risk description
- Probability (H/M/L)
- Impact (H/M/L)
- Mitigation plan
- Owner
**Use when**: Projects >2 weeks or high-stakes projects of any duration.
### todo-structure.md
Hierarchical task breakdown:
- Phases or milestones
- Tasks under each phase
- Subtasks if needed
- Metadata: owner, estimate, due date, dependencies
**Use when**: Always. Every project needs task breakdown.
### progress-update.md
Status reporting template:
- Completed since last update
- In progress
- Blockers
- Next steps
- Metrics/progress %
**Use when**: Projects needing regular status updates (weekly, sprint-based, etc.).
## Customization Notes
Templates are starting points. Common customizations:
- Remove sections that don't apply
- Add project-specific sections
- Adjust detail level based on audience
- Combine templates for simpler output
The goal is useful documentation, not template compliance.

463
skills/project-structures/SKILL.md
View File

@@ -1,463 +0,0 @@
---
name: project-structures
description: "PARA project initialization and lifecycle management. Use when: (1) creating new projects, (2) reviewing project status, (3) archiving completed projects, (4) structuring project files, (5) linking projects to areas. Triggers: new project, create project, project status, archive project."
compatibility: opencode
---
# Project Structures
PARA-based project creation, organization, and lifecycle management for Chiron system.
## Project Structure
```
01-projects/
├── work/
│ └── [project-name]/
│ ├── _index.md # Main project file (MOC)
│ ├── meetings/ # Meeting notes
│ ├── decisions/ # Decision records
│ ├── notes/ # General notes
│ └── resources/ # Project-specific resources
└── personal/
└── [project-name]/
└── [same structure]
```
## Create New Project
**When user says**: "Create project: X", "New project: X", "Start project: X", "/chiron-project X"
**Steps:**
1. **Parse project request:**
- Project name
- Context (work/personal) - ask if unspecified
- Deadline (if specified)
- Priority (if specified)
- Related area (if specified)
2. **Create project directory**:
- Path: `01-projects/[work|personal]/[project-name]/`
- Create subdirectories: `meetings/`, `decisions/`, `notes/`, `resources/`
3. **Create _index.md** using template:
- Template: `_chiron/templates/project.md`
- Fill in: title, status, deadline, priority, tags
- Set to `status: active`
4. **Create initial files:**
- `notes/_index.md` - Project notes index
- Link to related area if provided
5. **Confirm creation**
- Show project structure
- Ask: "Ready to add tasks?"
**Output format:**
```markdown
---
title: "Project Name"
status: active
created: 2026-01-27
deadline: 2026-03-31
priority: high
area: [[Area Name]]
tags: [work, development]
---
## Project Overview
[Brief description of what this project is about]
## Goals
1. [Goal 1]
2. [Goal 2]
3. [Goal 3]
## Success Criteria
- [Criteria 1]
- [Criteria 2]
- [Criteria 3]
## Timeline
- Start: 2026-01-27
- Milestone 1: 2026-02-15
- Milestone 2: 2026-03-15
- Deadline: 2026-03-31
## Tasks
See [[Project Tasks]] for full task list
## Resources
- [[Related Resource 1]]
- [[Related Resource 2]]
## Notes
See [[Project Notes]] for detailed notes
## Decisions
See [[Project Decisions]] for decision history
```
**Example:**
```
User: "Create project: Q1 Budget Review, work, critical, due March 15"
Action:
1. Parse: name="Q1 Budget Review", context="work", priority="critical", deadline="2026-03-15"
2. Create: 01-projects/work/q1-budget-review/
3. Create subdirectories
4. Create _index.md with template filled
5. Confirm: "Created Q1 Budget Review project in work. Ready to add tasks?"
```
## Project Status Review
**When user says**: "Project status", "Review projects", "How's project X going?"
**Steps:**
1. **Find project** (by name or list all)
2. **Read _index.md** for status and metadata
3. **Check task completion**:
- Read project task list (in `_index.md` or separate file)
- Calculate: completed vs total tasks
- Identify overdue tasks
4. **Check milestones**:
- Compare current date vs milestone dates
- Identify: on track, behind, ahead
5. **Generate status report**
**Output format:**
```markdown
# Project Status: Q1 Budget Review
## Current Status: 🟡 On Track
## Progress
- Tasks: 8/12 completed (67%)
- Deadline: 2026-03-15 (48 days remaining)
- Priority: Critical
## Milestones
- ✅ Milestone 1: Draft budget (Completed 2026-02-10)
- 🟡 Milestone 2: Review with team (Due 2026-02-20)
- ⏭️ Milestone 3: Final approval (Due 2026-03-15)
## Completed Tasks
- [x] Gather historical data
- [x] Draft initial budget
- [x] Review with finance team
## In Progress
- [ ] Address feedback from finance
- [ ] Prepare presentation for leadership
- [ ] Schedule review meeting
## Overdue
- [ ] Collect final approval signatures ⏫ 📅 2026-02-20 (DUE YESTERDAY)
## Blockers
- Leadership review delayed - waiting for director availability
## Recommendations
1. Follow up with director to schedule review meeting
2. Prioritize final approval task
3. Update team on timeline
## Related Notes
- [[Budget Review Meeting 2026-02-10]]
- [[Finance Team Notes]]
```
## Project Search & List
**When user says**: "List projects", "Show all projects", "Find project X"
**Steps:**
1. **Search project directories**:
- `rg "- status:" 01-projects --type md -A 2`
- Extract: title, status, deadline, priority
2. **Group by context** (work/personal)
3. **Sort by priority/deadline**
4. **Present summary**
**Output format:**
```markdown
# Active Projects
## Work Projects (4 active)
| Project | Priority | Deadline | Status | Progress |
|----------|-----------|-----------|----------|-----------|
| Q1 Budget Review | ⏫ Critical | 2026-03-15 | 🟡 On Track |
| Website Relaunch | 🔼 High | 2026-04-30 | 🟡 On Track |
| API Integration | 🔼 High | 2026-02-28 | 🔴 Behind |
| Team Onboarding | 🔽 Low | 2026-03-01 | 🟢 Ahead |
## Personal Projects (2 active)
| Project | Priority | Deadline | Status | Progress |
|----------|-----------|-----------|----------|-----------|
| Learn Rust | 🔼 High | 2026-04-30 | 🟡 On Track |
| Home Office Setup | 🔽 Low | 2026-02-15 | 🟢 Ahead |
## Summary
- Total active projects: 6
- Critical projects: 1
- Behind schedule: 1
- Projects with overdue tasks: 1
```
## Archive Project
**When user says**: "Archive project: X", "Complete project: X", "Project X is done"
**Steps:**
1. **Find project**
2. **Confirm completion**:
- Show project status
- Ask: "Is this project complete? All tasks done?"
3. **Update _index.md**:
- Set `status: completed`
- Add `completed_date: YYYY-MM-DD`
4. **Move to archive**:
- Source: `01-projects/[work|personal]/[project]/`
- Destination: `04-archive/projects/[work|personal]/[project]/`
5. **Update project _index.md** (if exists):
- Mark project as completed
- Add to completed list
6. **Confirm archive**
**Output format:**
```markdown
# Project Archived: Q1 Budget Review
## Archive Summary
- Status: ✅ Completed
- Completed date: 2026-03-14 (1 day before deadline)
- Location: 04-archive/projects/work/q1-budget-review/
## Outcomes
- Budget approved and implemented
- $50K savings identified
- New process documented
## Lessons Learned
1. Start stakeholder reviews earlier
2. Include finance team from beginning
3. Automated tools would reduce manual effort
## Related Resources
- [[Final Budget Document]]
- [[Process Documentation]]
```
## Project Notes Management
**When user says**: "Add note to project X", "Project X notes: [content]"
**Steps:**
1. **Find project directory**
2. **Create or update note** in `notes/`:
- Use timestamp for new notes
- Add frontmatter with date and tags
3. **Link to _index.md**:
- Update _index.md if it's the main project file
- Add to "Notes" section
4. **Confirm**
**Example:**
```
User: "Add note to Q1 Budget Review: Remember to check last year's Q1 for comparison"
Action:
Create 01-projects/work/q1-budget-review/notes/2026-02-01-comparison.md:
---
title: "Comparison with Last Year"
date: 2026-02-01
project: [[Q1 Budget Review]]
tags: [research, historical]
---
Check last year's Q1 budget for comparison points:
- Categories that increased significantly
- One-time expenses from last year
- Adjustments made mid-year
Confirm: "Added note to Q1 Budget Review."
```
## Decision Recording
**When user says**: "Record decision for project X", "Decision: [topic]", "Made a decision: [content]"
**Steps:**
1. **Create decision note** in `decisions/`:
- Filename: `decision-[topic]-YYYYMMDD.md`
- Use decision template
2. **Fill in sections**:
- Decision made
- Options considered
- Reasoning
- Impact
- Alternatives rejected
3. **Link to _index.md**
4. **Confirm**
**Output format:**
```markdown
---
title: "Decision: Use External Vendor"
date: 2026-02-15
project: [[Q1 Budget Review]]
tags: [decision, vendor, budget]
---
## Decision Made
Use External Vendor for cloud infrastructure instead of building internally.
## Context
Need to decide between internal build vs external purchase for cloud infrastructure.
## Options Considered
1. **Build internally**
- Pros: Full control, no recurring cost
- Cons: High initial cost, maintenance burden, 6-month timeline
2. **Purchase external**
- Pros: Quick deployment, no maintenance, lower risk
- Cons: Monthly cost, vendor lock-in
## Reasoning
- Timeline pressure (need by Q2)
- Team expertise is in product, not infrastructure
- Monthly cost is within budget
- Vendor has strong SLA guarantees
## Impact
- Project timeline reduced by 4 months
- $120K savings in development cost
- Monthly operational cost: $2,000
- Reduced risk of project failure
## Alternatives Rejected
- Build internally: Too slow and expensive for current timeline
## Next Actions
- [ ] Contract vendor by 2026-02-20
- [ ] Plan migration by 2026-03-01
- [ ] Budget review by 2026-03-15
```
## Project-Area Linking
**When user says**: "Link project to area", "Project X belongs to area Y"
**Steps:**
1. **Read project _index.md**
2. **Find or create area file**:
- Location: `02-areas/[work|personal]/[area].md`
3. **Update project _index.md**:
- Add `area: [[Area Name]]` to frontmatter
- Update links section
4. **Update area file**:
- Add project to area's project list
- Link back to project
**Example:**
```
User: "Link Q1 Budget Review to Finances area"
Action:
1. Read 01-projects/work/q1-budget-review/_index.md
2. Read 02-areas/personal/finances.md
3. Update project _index.md frontmatter:
area: [[Finances]]
4. Update finances.md:
## Active Projects
- [[Q1 Budget Review]]
Confirm: "Linked Q1 Budget Review to Finances area."
```
## Integration with Other Skills
**Delegates to:**
- `obsidian-management` - File operations and templates
- `chiron-core` - PARA methodology guidance
- `task-management` - Project task lists
- `quick-capture` - Quick meeting/decision capture
- `meeting-notes` - Meeting note templates
**Delegation rules:**
- File creation → `obsidian-management`
- Task operations → `task-management`
- PARA guidance → `chiron-core`
- Meeting/decision templates → `meeting-notes`
## Best Practices
### Creating Projects
- Use clear, descriptive names
- Set realistic deadlines
- Define success criteria
- Link to areas immediately
- Create task list early
### Managing Projects
- Update status regularly
- Document decisions
- Track progress visibly
- Celebrate milestones
- Learn from completed projects
### Archiving
- Document outcomes
- Capture lessons learned
- Keep accessible for reference
- Update area health after archive
## Quick Reference
| Action | Command Pattern |
|--------|-----------------|
| Create project | "Create project: [name] [work|personal]" |
| Project status | "Project status: [name]" or "Review projects" |
| Archive project | "Archive project: [name]" or "Complete project: [name]" |
| Add note | "Add note to project [name]: [content]" |
| Record decision | "Decision: [topic] for project [name]" |
| Link to area | "Link project [name] to area [area]" |
## Error Handling
### Project Already Exists
1. Ask user: "Update existing or create variant?"
2. If update: Open existing _index.md
3. If variant: Create with version suffix
### Area Not Found
1. Ask user: "Create new area [name]?"
2. If yes: Create area file
3. Link project to new area
### Archive Conflicts
1. Check if already in archive
2. Ask: "Overwrite or create new version?"
3. Use timestamp if keeping both
## Resources
- `references/project-templates.md` - Project initiation templates
- `references/decision-frameworks.md` - Decision-making tools
- `assets/project-structure/` - Project file templates
**Load references when:**
- Customizing project templates
- Complex decision-making
- Project troubleshooting

324
skills/quick-capture/SKILL.md
View File

@@ -1,324 +0,0 @@
---
name: quick-capture
description: "Minimal friction inbox capture for Chiron system. Use when: (1) capturing quick thoughts, (2) adding tasks, (3) saving meeting notes, (4) recording learnings, (5) storing ideas. Triggers: capture, quick note, remember, save this, todo, inbox."
compatibility: opencode
---
# Quick Capture
Minimal friction capture to `00-inbox/` for later processing.
## Philosophy
**Capture everything now, organize later.**
The inbox is a temporary holding area. Speed is prioritized over structure. Processing happens during weekly review.
## Capture Types
### Task Capture
**When user says**: "Add task: X", "Remember to X", "Todo: X"
**Steps:**
1. Parse task from request:
- Task description
- Priority (if specified)
- Due date (if specified)
- Tags (if specified)
2. Create task in `tasks/inbox.md`:
```markdown
- [ ] [Task description] #inbox ⏫ 📅 [date if specified]
```
3. Confirm capture
**Examples:**
```
User: "Capture: Review Q1 budget proposal"
Action:
Create task in tasks/inbox.md:
- [ ] Review Q1 budget proposal #inbox ⏫
Confirm: "Captured to inbox. Process during weekly review."
```
```
User: "Add task: Email John about project deadline, due Friday"
Action:
Create task in tasks/inbox.md:
- [ ] Email John about project deadline #inbox 🔼 📅 2026-01-31
Confirm: "Captured to inbox. Process during weekly review."
```
### Note Capture
**When user says**: "Note: X", "Capture this: X", "Remember: X"
**Steps:**
1. Create note in `00-inbox/` with timestamp:
- Filename: `quick-capture-YYYYMMDD-HHMM.md`
- Content: Captured text with tags
2. Add frontmatter with creation date
3. Confirm capture
**Examples:**
```
User: "Capture this: Obsidian plugin that syncs with Notion would be amazing. Need to research this."
Action:
Create 00-inbox/quick-capture-20260127-1730.md:
---
title: "Obsidian-Notion sync plugin idea"
tags: [idea, obsidian]
created: 2026-01-27
---
Obsidian plugin that syncs with Notion would be amazing. Need to research this.
Confirm: "Captured to inbox."
```
### Meeting Capture
**When user says**: "Meeting notes: X", "Just finished meeting with X", "Capture meeting about X"
**Steps:**
1. Create meeting note in `00-inbox/meetings/`:
- Filename: `meeting-[topic]-YYYYMMDD.md`
- Use meeting template if available
2. Fill in: attendees, key points, action items
3. Link to project if mentioned
**Examples:**
```
User: "Meeting notes: Product roadmap discussion with team"
Action:
Create 00-inbox/meetings/product-roadmap-20260127.md:
---
title: "Product Roadmap Discussion"
date: 2026-01-27
attendees: [Team]
tags: [meeting, work]
---
## Attendees
- [Person 1]
- [Person 2]
## Agenda
- Review Q1 roadmap
- Discuss feature prioritization
## Key Points
- ...
## Action Items
- [ ] Create JIRA tickets for Q1 features
- [ ] Schedule follow-up with design team
- [ ] Update stakeholders
Confirm: "Captured meeting notes to inbox."
```
### Learning Capture
**When user says**: "Learned X", "Discovery: X", "Insight: X"
**Steps:**
1. Create learning note in `00-inbox/`:
- Filename: `learning-[topic]-YYYYMMDD.md`
- Content: What was learned, context, applications
2. Add tags: `#learning`, `#[domain]`
3. Confirm capture
**Examples:**
```
User: "Learned: Git rebase vs merge - use rebase for local history, merge for shared branches"
Action:
Create 00-inbox/learning-git-rebase-merge-20260127.md:
---
title: "Git: Rebase vs Merge"
tags: [learning, git, programming]
created: 2026-01-27
---
## Learning
Use rebase for local history cleanup, merge for shared branches.
## Context
Reading about Git workflows. Confusion about when to use each.
## Applications
- Local feature branch before push: Rebase
- Updating shared branch: Merge
- Cleaning up history: Rebase -i
Confirm: "Captured learning to inbox."
```
### Web Clip / Reference Capture
**When user says**: "Save this article: URL", "Clip this: X", "Reference: X"
**Steps:**
1. Create reference in `00-inbox/web-clips/`:
- Filename: `[source]-[topic].md`
- Content: Title, URL, summary, key takeaways
2. Add tags for topic and source
3. Link to relevant areas/projects if obvious
**Examples:**
```
User: "Save this: article about PARA method from Forte Labs"
Action:
Create 00-inbox/web-clips/forte-labs-para.md:
---
title: "PARA Method - Forte Labs"
source: https://fortelabs.com/blog/para/
tags: [productivity, para, organization]
saved: 2026-01-27
---
## Source
[PARA Method - Forte Labs](https://fortelabs.com/blog/para/)
## Summary
Comprehensive guide to PARA method for organizing digital information. Projects, Areas, Resources, Archive.
## Key Takeaways
- Projects = short-term, deadline-driven
- Areas = ongoing responsibilities
- Resources = reference material
- Archive = completed/inactive
## Applications
- Reorganize my knowledge vault using PARA
- Clear out old inbox items
Confirm: "Saved reference to inbox."
```
## File Structure
```
00-inbox/
├── quick-capture-*.md # Quick thoughts and notes
├── meetings/ # Unprocessed meeting notes
│ └── meeting-*.md
├── web-clips/ # Saved articles and references
│ └── [source]-*.md
└── learnings/ # Captured learnings
└── learning-*.md
```
## Processing Inbox
**Trigger**: During weekly review (`/chiron-review`)
**Processing workflow:**
1. **For each item in inbox:**
- Read content
- Determine PARA category (consult `chiron-core`)
- Move to appropriate location
2. **Task processing:**
- Add to project task list if project-specific
- Add to area task list if area-specific
- Keep in `tasks/inbox.md` if general
3. **Note processing:**
- Move to `03-resources/` if reference material
- Move to `01-projects/` if project-specific
- Move to `02-areas/` if area-specific
- Archive to `04-archive/` if no longer relevant
4. **Delete irrelevant items**
**Example:**
```
Inbox has:
- Task: "Buy groceries" → Move to 02-areas/personal/health.md
- Note: "Obsidian tips" → Move to 03-resources/tools/obsidian.md
- Task: "Finish project X" → Move to 01-projects/work/project-x/_index.md
- Old reference from 2022 → Move to 04-archive/
```
## Best Practices
### Speed Over Structure
- Don't categorize during capture
- Don't add tags during capture
- Don't create projects during capture
- Focus on getting it out of your head
### Minimal Metadata
- Only add what's immediately obvious
- Date is automatic (filename or frontmatter)
- Don't overthink tags
### Batch Processing
- Process inbox during weekly review
- Don't process individually (except for urgent items)
- Group similar items when organizing
### Urgent Items
- If user specifies "urgent" or "critical":
- Create directly in appropriate location (not inbox)
- Add high priority (⏫)
- Confirm: "This is urgent, created directly in [location]"
## Integration with Other Skills
**Delegates to:**
- `obsidian-management` - File creation and operations
- `chiron-core` - PARA methodology for processing inbox
- `daily-routines` - Inbox processing during weekly review
**Delegation rules:**
- Processing inbox → `daily-routines` (weekly review)
- Moving files → `obsidian-management`
- PARA categorization → `chiron-core`
## Quick Reference
| Capture Type | Command Pattern | Location |
|-------------|-----------------|------------|
| Task | "Capture: [task]" or "Todo: [task]" | tasks/inbox.md |
| Note | "Note: [content]" or "Remember: [content]" | 00-inbox/quick-capture-*.md |
| Meeting | "Meeting notes: [topic]" | 00-inbox/meetings/meeting-*.md |
| Learning | "Learned: [insight]" | 00-inbox/learnings/learning-*.md |
| Reference | "Save: [article]" or "Clip: [URL]" | 00-inbox/web-clips/[source]-*.md |
## Error Handling
### Inbox Directory Not Found
1. Create `00-inbox/` directory
2. Create subdirectories: `meetings/`, `web-clips/`, `learnings/`
3. Confirm structure created
### File Already Exists
1. Add timestamp to filename (if not present)
2. Or append to existing file
3. Ask user which approach
### Processing Conflicts
1. Ask user for clarification on PARA placement
2. Provide options with reasoning
3. Let user choose
## Resources
- `references/inbox-organization.md` - Detailed processing workflows
- `references/capture-formats.md` - Format specifications by type
**Load references when:**
- Detailed processing questions
- Format customization needed
- Troubleshooting organization issues

59
skills/research/SKILL.md
View File

@@ -1,59 +0,0 @@
---
name: research
description: "Research and investigation workflows. Use when: (1) researching technologies or tools, (2) investigating best practices, (3) comparing solutions, (4) gathering information for decisions, (5) deep-diving into topics. Triggers: research, investigate, explore, compare, learn about, what are best practices for, how does X work."
compatibility: opencode
---
# Research
Research and investigation workflows for informed decision-making.
## Status: Stub
This skill is a placeholder for future development. Core functionality to be added:
## Planned Features
### Investigation Workflow
- Multi-source research (web, docs, code)
- Source credibility assessment
- Summary with drill-down capability
### Technology Evaluation
- Feature comparison matrices
- Pros/cons analysis
- Fit-for-purpose assessment
### Best Practices Discovery
- Industry standards lookup
- Implementation patterns
- Common pitfalls
### Learning Path Generation
- Topic breakdown
- Resource recommendations
- Progress tracking
### Output to Obsidian
- Save research findings as resource notes
- Create learning notes for topics
- Link related resources using WikiLinks
## Integration Points
- **Obsidian**: Save research findings to Resources (03-resources/)
- **Web Search**: Primary research source
- **librarian agent**: External documentation lookup
## Quick Commands (Future)
| Command | Description |
|---------|-------------|
| `research [topic]` | Start research session |
| `compare [A] vs [B]` | Feature comparison |
| `best practices [topic]` | Lookup standards |
| `learn [topic]` | Generate learning path |
## Notes
Expand this skill based on actual research patterns that emerge from usage.

406
skills/task-management/SKILL.md
View File

@@ -1,406 +0,0 @@
---
name: task-management
description: "PARA-based task management using Obsidian Tasks plugin format. Use when: (1) creating/managing tasks, (2) daily or weekly reviews, (3) prioritizing work, (4) searching for tasks, (5) planning sprints or focus blocks. Triggers: task, todo, find tasks, search tasks, overdue, prioritize."
compatibility: opencode
---
# Task Management
PARA-based task management using Obsidian Tasks plugin format for Chiron system.
## Obsidian Tasks Format
**Basic format:**
```markdown
- [ ] Task description #tag ⏫ 📅 YYYY-MM-DD
```
**Priority indicators:**
- ⏫ = Critical (urgent AND important)
- 🔼 = High (important, not urgent)
- 🔽 = Low (nice to have)
**Date indicators:**
- 📅 = Due date
- ⏳ = Start date
- 🛫 = Scheduled date
**Owner attribution:**
```markdown
- [ ] Task description #todo 👤 @owner ⏫ 📅 YYYY-MM-DD
```
## Task Locations
```
~/CODEX/
├── tasks/ # Central task management
│ ├── inbox.md # Unprocessed tasks
│ ├── waiting.md # Blocked/delegated
│ ├── someday.md # Future ideas
│ └── by-context/ # Context-based task lists
│ ├── work.md
│ ├── home.md
│ └── errands.md
├── 01-projects/ # Project-specific tasks (in _index.md or notes/tasks.md)
└── 02-areas/ # Area-specific tasks (in area files)
```
## Core Workflows
### Create Task
**When user says**: "Add task: X", "Todo: X", "Remember to: X"
**Steps:**
1. **Parse task from request:**
- Task description
- Priority (if specified: critical, high, low)
- Due date (if specified)
- Owner (if specified: @mention)
- Context (if specified)
- Project/area (if specified)
2. **Determine location:**
- Project-specific → `01-projects/[project]/_index.md` or `tasks.md`
- Area-specific → `02-areas/[area].md`
- General → `tasks/inbox.md`
3. **Create task in Obsidian format:**
```markdown
- [ ] [Task description] #tag [priority] 👤 [@owner] 📅 [date]
```
4. **Confirm creation**
**Examples:**
```
User: "Add task: Review Q1 budget proposal, critical, due Friday"
Action:
Create in tasks/inbox.md:
- [ ] Review Q1 budget proposal #inbox ⏫ 📅 2026-01-31
Confirm: "Created task in inbox."
```
```
User: "Task: Email John about project deadline, due Friday, @john"
Action:
Create in tasks/inbox.md:
- [ ] Email John about project deadline #inbox 🔼 👤 @john 📅 2026-01-31
Confirm: "Created task assigned to John."
```
```
User: "Add task to Project X: Create PRD, high priority"
Action:
Create in 01-projects/work/project-x/_index.md:
- [ ] Create PRD #high 📅 2026-02-15
Confirm: "Created task in Project X."
```
### Find Tasks
**When user says**: "Find tasks", "What tasks do I have?", "Show me tasks for [context/project]"
**Steps:**
1. **Determine search scope:**
- All tasks → Search all task files
- Context tasks → Search `tasks/by-context/[context].md`
- Project tasks → Read project's `_index.md` or `tasks.md`
- Area tasks → Read area file
- Overdue tasks → Search for tasks with past due dates
2. **Search using rg:**
```bash
# Find all tasks
rg "- \\[ \\]" ~/CODEX --type md
# Find tasks by tag
rg "#work" ~/CODEX --type md
# Find overdue tasks
rg "- \\[ \\].*📅" ~/CODEX --type md | filter-past-dates
```
3. **Parse and organize:**
- Extract task description
- Extract priority indicators (⏫/🔼/🔽)
- Extract due dates
- Extract owners (@mentions)
- Extract tags
4. **Present results grouped by:**
- Priority
- Due date
- Context/project/area
**Output format:**
```markdown
# Found 15 tasks
## Critical Tasks (⏫)
1. [ ] Review Q1 budget #work ⏫ 📅 2026-01-31
2. [ ] Client presentation #work ⏫ 📅 2026-01-30
## High Priority (🔼)
1. [ ] Update documentation #project-a 🔼 📅 2026-02-15
2. [ ] Team meeting notes #work 🔼 👤 @john
3. [ ] Buy groceries #personal 🔼 📅 2026-01-28
## Upcoming (by due date)
This week:
- [ ] Submit expense report #work 🔼 📅 2026-01-29
- [ ] Dentist appointment #personal 🔼 📅 2026-01-30
Next week:
- [ ] Project milestone #work 🔼 📅 2026-02-05
- [ ] Car service #personal 🔼 📅 2026-02-07
## By Owner
Assigned to @john (2 tasks):
- [ ] Team meeting notes #work 🔼
- [ ] Email stakeholder #work 🔼 📅 2026-02-01
```
### Search Specific Contexts
**When user says**: "What [context] tasks do I have?", "Show work tasks", "Show personal tasks"
**Steps:**
1. **Read context file**: `tasks/by-context/[context].md`
2. **Parse tasks**
3. **Present filtered list**
**Available contexts:**
- `work.md` - Work-related tasks
- `home.md` - Household/admin tasks
- `errands.md` - Shopping/running errands
- `deep-work.md` - Focus work (no interruptions)
- `calls.md` - Phone/video calls
- `admin.md` - Administrative tasks
### Prioritize Tasks
**When user says**: "Prioritize my tasks", "What should I work on?", "Focus check"
**Steps:**
1. **Fetch all incomplete tasks**:
- `rg "- \\[ \\]" ~/CODEX --type md`
- Filter out completed (`[x]`)
2. **Sort by criteria:**
- Priority (⏫ > 🔼 > 🔽 > no indicator)
- Due date (sooner first)
- Energy level (if specified: high/medium/low)
3. **Return top 3-5 tasks**
4. **Include rationale** for prioritization
**Output format:**
```markdown
# Focus Recommendations (5 tasks found)
## Top Priority: ⏫ Critical
1. **[Review Q1 budget]** #work ⏫ 📅 2026-01-31
- Why: Due in 4 days, critical for Q2 planning
- Area: Finances
- Estimated time: 2 hours
## High Priority: 🔼 Important (due within week)
1. **[Client presentation]** #work 🔼 📅 2026-01-30
- Why: Client commitment, high impact
- Area: Work
- Estimated time: 4 hours
2. **[Team standup]** #work 🔼
- Why: Daily sync, keeps team aligned
- Area: Work
- Estimated time: 30 minutes
3. **[Car registration]** #personal 🔼 📅 2026-02-01
- Why: Legal requirement, must complete
- Area: Home
- Estimated time: 1 hour
## Recommended Order
1. Team standup (30min, energizes for day)
2. Review Q1 budget (2 hours, critical, morning focus)
3. Client presentation (4 hours, high energy block)
4. Car registration (1 hour, after lunch)
## Not Now (someday)
- [ ] Learn Rust #personal 🔽
- [ ] Organize photos #personal 🔽
```
### Update Task Status
**When user says**: "Mark task X as done", "Complete: X", "Task X finished"
**Steps:**
1. **Find task** (by description or show options)
2. **Change checkbox:**
```markdown
# Before:
- [ ] Task description
# After:
- [x] Task description
```
3. **Update modified date** in frontmatter (if present)
4. **Confirm**
### Move Tasks
**When user says**: "Move task X to project Y", "Task X goes to area Z"
**Steps:**
1. **Find source task**
2. **Read target location** (project `_index.md` or area file)
3. **Move task** (copy to target, delete from source)
4. **Update task context/tags** if needed
5. **Confirm**
**Example:**
```
User: "Move 'Buy groceries' to Finances area"
Action:
1. Find task in tasks/inbox.md
2. Read 02-areas/personal/finances.md
3. Copy task to finances.md
4. Delete from tasks/inbox.md
5. Confirm: "Moved 'Buy groceries' to Finances area."
```
### Task Delegation/Blocking
**When user says**: "Delegate task X to Y", "Task X is blocked", "Waiting for X"
**Steps:**
1. **Find task**
2. **Add owner or blocking info:**
```markdown
# Delegation:
- [ ] Task description #waiting 👤 @owner ⏫ 📅 date
# Blocked:
- [ ] Task description #waiting 🛑 Blocked by: [reason]
```
3. **Move to `tasks/waiting.md`** if delegated/blocked
4. **Confirm**
## Integration with Other Skills
**Delegates to:**
- `obsidian-management` - File operations (create/update/delete tasks)
- `chiron-core` - PARA methodology for task placement
- `daily-routines` - Task prioritization and scheduling
- `project-structures` - Project task lists
- `meeting-notes` - Extract action items from meetings
**Delegation rules:**
- File operations → `obsidian-management`
- PARA placement → `chiron-core`
- Project tasks → `project-structures`
- Meeting actions → `meeting-notes`
## Quick Reference
| Action | Command Pattern | Location |
|--------|-----------------|------------|
| Create task | "Task: [description] [priority] [due] [@owner]" | tasks/inbox.md or project/area |
| Find tasks | "Find tasks" or "What tasks do I have?" | All task files |
| Context tasks | "Show [context] tasks" | tasks/by-context/[context].md |
| Prioritize | "Prioritize tasks" or "What should I work on?" | All tasks, sorted |
| Mark done | "Task [description] done" or "Complete: [description]" | Task location |
| Move task | "Move task [description] to [project/area]" | Target location |
| Defer | "Someday: [task]" or "Defer: [task]" | tasks/someday.md |
## Best Practices
### Creating Tasks
- Be specific (not vague like "follow up")
- Set realistic due dates
- Assign owners clearly
- Link to projects/areas immediately
- Use appropriate priorities
### Managing Tasks
- Review daily (delegate to daily-routines)
- Process inbox weekly
- Archive completed tasks regularly
- Update context when tasks move
### Searching Tasks
- Use tags for filtering
- Search by context when batching
- Check overdue tasks daily
- Review waiting tasks weekly
## Error Handling
### Task Not Found
1. Search similar tasks
2. Ask user: "Which task?"
3. List options with context
### Duplicate Tasks
1. Detect duplicates by description
2. Ask: "Merge or keep separate?"
3. If merge, combine due dates/priorities
### Location Not Found
1. Create directory structure
2. Ask user: "Create in this location?"
3. Create task in inbox as fallback
## Resources
- `references/task-formats.md` - Obsidian Tasks plugin syntax
- `references/prioritization-methods.md` - Eisenhower matrix, energy-based prioritization
- `references/search-patterns.md` - rg patterns for finding tasks
**Load references when:**
- Format questions arise
- Prioritization help needed
- Search issues occur
- Task automation questions
## Obsidian Tasks Plugin Configuration
For full functionality, configure Obsidian Tasks plugin:
**Settings:**
- Task format: `- [ ] Task #tag ⏫ 📅 YYYY-MM-DD`
- Priority symbols: ⏫, 🔼, 🔽
- Date format: YYYY-MM-DD
- Default file: tasks/inbox.md
**Queries:**
```dataview
TASK
WHERE !completed
GROUP BY priority
SORT due date ASC
```
```dataview
TASK
WHERE !completed AND due < date(today)
SORT due ASC
GROUP BY project
```