Update Obsidian vault path from ~/knowledge to ~/CODEX
This commit is contained in:
m3tm3re
223
skills/chiron-core/SKILL.md
Normal file
223
skills/chiron-core/SKILL.md
Normal file
@@ -0,0 +1,223 @@
|
||||
---
|
||||
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
Normal file
272
skills/chiron-core/references/para-guide.md
Normal file
@@ -0,0 +1,272 @@
|
||||
# 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
|
||||
270
skills/chiron-core/references/priority-matrix.md
Normal file
270
skills/chiron-core/references/priority-matrix.md
Normal file
@@ -0,0 +1,270 @@
|
||||
# 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
Normal file
288
skills/chiron-core/references/reflection-questions.md
Normal file
@@ -0,0 +1,288 @@
|
||||
# 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)
|
||||
Reference in New Issue
Block a user