Update Obsidian vault path from ~/knowledge to ~/CODEX
This commit is contained in:
m3tm3re
@@ -1,246 +1,406 @@
|
||||
---
|
||||
name: task-management
|
||||
description: "PARA-based task and project management with Anytype integration. Use when: (1) creating/managing tasks or projects, (2) daily or weekly reviews, (3) prioritizing work, (4) capturing action items, (5) planning sprints or focus blocks, (6) asking 'what should I work on?'. Triggers: task, todo, project, priority, review, focus, plan, backlog, inbox, capture."
|
||||
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 productivity system integrated with Anytype for Sascha's personal and professional task management.
|
||||
PARA-based task management using Obsidian Tasks plugin format for Chiron system.
|
||||
|
||||
## Quick Reference
|
||||
## Obsidian Tasks Format
|
||||
|
||||
| Action | Command Pattern |
|
||||
|--------|-----------------|
|
||||
| Quick capture | "Capture: [item]" or "Add to inbox: [item]" |
|
||||
| Create task | "Task: [title] for [area/project]" |
|
||||
| Create project | "New project: [title] in [area]" |
|
||||
| Daily review | "Daily review" or "What's on for today?" |
|
||||
| Weekly review | "Weekly review" or "Week planning" |
|
||||
| Focus check | "What should I focus on?" |
|
||||
| Context batch | "What [area] tasks can I batch?" |
|
||||
**Basic format:**
|
||||
```markdown
|
||||
- [ ] Task description #tag ⏫ 📅 YYYY-MM-DD
|
||||
```
|
||||
|
||||
## Anytype Configuration
|
||||
**Priority indicators:**
|
||||
- ⏫ = Critical (urgent AND important)
|
||||
- 🔼 = High (important, not urgent)
|
||||
- 🔽 = Low (nice to have)
|
||||
|
||||
**Space**: Chiron (create if not exists)
|
||||
**Date indicators:**
|
||||
- 📅 = Due date
|
||||
- ⏳ = Start date
|
||||
- 🛫 = Scheduled date
|
||||
|
||||
### Types
|
||||
**Owner attribution:**
|
||||
```markdown
|
||||
- [ ] Task description #todo 👤 @owner ⏫ 📅 YYYY-MM-DD
|
||||
```
|
||||
|
||||
| Type | PARA Category | Purpose |
|
||||
|------|---------------|---------|
|
||||
| `project` | Projects | Active outcomes with deadlines |
|
||||
| `area` | Areas | Ongoing responsibilities |
|
||||
| `resource` | Resources | Reference materials |
|
||||
| `task` | (within Projects/Areas) | Individual action items |
|
||||
| `note` | (Inbox/Resources) | Quick captures, meeting notes |
|
||||
## Task Locations
|
||||
|
||||
### Key Properties
|
||||
|
||||
| Property | Type | Used On | Values |
|
||||
|----------|------|---------|--------|
|
||||
| `status` | select | Task, Project | `inbox`, `next`, `waiting`, `scheduled`, `done` |
|
||||
| `priority` | select | Task, Project | `critical`, `high`, `medium`, `low` |
|
||||
| `area` | relation | Task, Project | Links to Area objects |
|
||||
| `due_date` | date | Task, Project | Deadline |
|
||||
| `energy` | select | Task | `high`, `medium`, `low` |
|
||||
| `context` | multi_select | Task | `deep-work`, `admin`, `calls`, `errands` |
|
||||
```
|
||||
~/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
|
||||
|
||||
### 1. Quick Capture
|
||||
### Create Task
|
||||
|
||||
Minimal friction inbox capture. Process later during review.
|
||||
**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: "Capture: Review Q1 budget proposal"
|
||||
User: "Add task: Review Q1 budget proposal, critical, due Friday"
|
||||
|
||||
Action:
|
||||
1. Create note in Anytype with status=inbox
|
||||
2. Confirm: "Captured to inbox. 12 items pending processing."
|
||||
Create in tasks/inbox.md:
|
||||
- [ ] Review Q1 budget proposal #inbox ⏫ 📅 2026-01-31
|
||||
|
||||
Confirm: "Created task in inbox."
|
||||
```
|
||||
|
||||
### 2. Create Task
|
||||
|
||||
Full task with metadata for proper routing.
|
||||
|
||||
```
|
||||
User: "Task: Prepare board presentation for CTO Leadership, high priority, due Friday"
|
||||
User: "Task: Email John about project deadline, due Friday, @john"
|
||||
|
||||
Action:
|
||||
1. Find or create "CTO Leadership" area in Anytype
|
||||
2. Create task object:
|
||||
- name: "Prepare board presentation"
|
||||
- area: [CTO Leadership object ID]
|
||||
- priority: high
|
||||
- due_date: [this Friday]
|
||||
- status: next
|
||||
3. Confirm with task details
|
||||
Create in tasks/inbox.md:
|
||||
- [ ] Email John about project deadline #inbox 🔼 👤 @john 📅 2026-01-31
|
||||
|
||||
Confirm: "Created task assigned to John."
|
||||
```
|
||||
|
||||
### 3. Create Project
|
||||
|
||||
Projects are outcomes with multiple tasks and a completion state.
|
||||
|
||||
```
|
||||
User: "New project: Launch NixOS Flakes Course in m3ta.dev area"
|
||||
User: "Add task to Project X: Create PRD, high priority"
|
||||
|
||||
Action:
|
||||
1. Find "m3ta.dev" area
|
||||
2. Create project object:
|
||||
- name: "Launch NixOS Flakes Course"
|
||||
- area: [m3ta.dev object ID]
|
||||
- status: active
|
||||
3. Prompt: "What are the key milestones or first tasks?"
|
||||
4. Create initial tasks if provided
|
||||
Create in 01-projects/work/project-x/_index.md:
|
||||
- [ ] Create PRD #high 📅 2026-02-15
|
||||
|
||||
Confirm: "Created task in Project X."
|
||||
```
|
||||
|
||||
### 4. Daily Review (Evening)
|
||||
### Find Tasks
|
||||
|
||||
Run each evening to close the day and prep tomorrow.
|
||||
**When user says**: "Find tasks", "What tasks do I have?", "Show me tasks for [context/project]"
|
||||
|
||||
**Workflow** - See [references/review-templates.md](references/review-templates.md) for full template.
|
||||
**Steps:**
|
||||
|
||||
Steps:
|
||||
1. **Fetch today's completed** - Celebrate wins
|
||||
2. **Fetch incomplete tasks** - Reschedule or note blockers
|
||||
3. **Check inbox** - Quick process or defer to weekly
|
||||
4. **Tomorrow's priorities** - Identify top 3 for morning focus
|
||||
5. **Send summary via ntfy** (if configured)
|
||||
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
|
||||
|
||||
```
|
||||
User: "Daily review"
|
||||
2. **Search using rg:**
|
||||
```bash
|
||||
# Find all tasks
|
||||
rg "- \\[ \\]" ~/CODEX --type md
|
||||
|
||||
Output format:
|
||||
## Daily Review - [Date]
|
||||
# Find tasks by tag
|
||||
rg "#work" ~/CODEX --type md
|
||||
|
||||
### Completed Today
|
||||
- [x] Task 1
|
||||
- [x] Task 2
|
||||
# Find overdue tasks
|
||||
rg "- \\[ \\].*📅" ~/CODEX --type md | filter-past-dates
|
||||
```
|
||||
|
||||
### Carried Forward
|
||||
- [ ] Task 3 (rescheduled to tomorrow)
|
||||
- [ ] Task 4 (blocked: waiting on X)
|
||||
3. **Parse and organize:**
|
||||
- Extract task description
|
||||
- Extract priority indicators (⏫/🔼/🔽)
|
||||
- Extract due dates
|
||||
- Extract owners (@mentions)
|
||||
- Extract tags
|
||||
|
||||
### Inbox Items: 5 pending
|
||||
4. **Present results grouped by:**
|
||||
- Priority
|
||||
- Due date
|
||||
- Context/project/area
|
||||
|
||||
### Tomorrow's Top 3
|
||||
1. [Highest impact task]
|
||||
2. [Second priority]
|
||||
3. [Third priority]
|
||||
**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
|
||||
```
|
||||
|
||||
### 5. Weekly Review
|
||||
### Search Specific Contexts
|
||||
|
||||
Comprehensive PARA review. See [references/para-methodology.md](references/para-methodology.md).
|
||||
**When user says**: "What [context] tasks do I have?", "Show work tasks", "Show personal tasks"
|
||||
|
||||
**Workflow**:
|
||||
1. **Get Clear** - Process inbox to zero
|
||||
2. **Get Current** - Review each Area's active projects
|
||||
3. **Get Creative** - Identify new projects or opportunities
|
||||
4. **Plan Week** - Set weekly outcomes and time blocks
|
||||
**Steps:**
|
||||
|
||||
```
|
||||
User: "Weekly review"
|
||||
1. **Read context file**: `tasks/by-context/[context].md`
|
||||
2. **Parse tasks**
|
||||
3. **Present filtered list**
|
||||
|
||||
Process:
|
||||
1. List all inbox items -> prompt to process each
|
||||
2. For each Area, show active projects and their status
|
||||
3. Flag stalled projects (no activity 7+ days)
|
||||
4. Identify completed projects -> move to archive
|
||||
5. Prompt for new commitments
|
||||
6. Output weekly plan
|
||||
**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 🔽
|
||||
```
|
||||
|
||||
### 6. Priority Focus
|
||||
### Update Task Status
|
||||
|
||||
Impact-first prioritization using Sascha's preferences.
|
||||
**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: "What should I focus on?"
|
||||
|
||||
Logic:
|
||||
1. Fetch tasks where status=next, sorted by:
|
||||
- priority (critical > high > medium > low)
|
||||
- due_date (sooner first)
|
||||
- energy match (if time of day known)
|
||||
2. Return top 3-5 with rationale
|
||||
3. Consider context batching opportunities
|
||||
|
||||
Output:
|
||||
## Focus Recommendations
|
||||
|
||||
**Top Priority**: [Task]
|
||||
- Why: [Impact statement]
|
||||
- Area: [Area name]
|
||||
- Due: [Date or "no deadline"]
|
||||
|
||||
**Also Important**:
|
||||
1. [Task 2] - [brief why]
|
||||
2. [Task 3] - [brief why]
|
||||
|
||||
**Batching Opportunity**: You have 3 [context] tasks that could be done together.
|
||||
```
|
||||
|
||||
### 7. Context Batching
|
||||
|
||||
Group similar tasks for focused execution.
|
||||
|
||||
```
|
||||
User: "What admin tasks can I batch?"
|
||||
User: "Move 'Buy groceries' to Finances area"
|
||||
|
||||
Action:
|
||||
1. Fetch tasks where context contains "admin"
|
||||
2. Group by area
|
||||
3. Estimate total time
|
||||
4. Suggest execution order
|
||||
|
||||
Output:
|
||||
## Admin Task Batch
|
||||
|
||||
**Estimated time**: ~45 minutes
|
||||
|
||||
1. [ ] Reply to vendor email (CTO Leadership) - 10min
|
||||
2. [ ] Approve expense reports (CTO Leadership) - 15min
|
||||
3. [ ] Update team wiki (CTO Leadership) - 20min
|
||||
|
||||
Ready to start? I can track completion.
|
||||
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."
|
||||
```
|
||||
|
||||
## Notification Integration (ntfy)
|
||||
### Task Delegation/Blocking
|
||||
|
||||
Send notifications for:
|
||||
- Daily review summary (evening)
|
||||
- Overdue task alerts
|
||||
- Weekly review reminder (Sunday evening)
|
||||
**When user says**: "Delegate task X to Y", "Task X is blocked", "Waiting for X"
|
||||
|
||||
Format for ntfy:
|
||||
```bash
|
||||
curl -d "Daily Review: 5 completed, 3 for tomorrow. Top priority: [task]" \
|
||||
ntfy.sh/sascha-chiron
|
||||
**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
|
||||
```
|
||||
|
||||
Configure topic in environment or Anytype settings.
|
||||
|
||||
## Anytype API Patterns
|
||||
|
||||
See [references/anytype-workflows.md](references/anytype-workflows.md) for:
|
||||
- Space and type setup
|
||||
- CRUD operations for tasks/projects
|
||||
- Query patterns for reviews
|
||||
- Batch operations
|
||||
|
||||
## PARA Methodology Reference
|
||||
|
||||
See [references/para-methodology.md](references/para-methodology.md) for:
|
||||
- PARA category definitions
|
||||
- When to use Projects vs Areas
|
||||
- Archive criteria
|
||||
- Maintenance rhythms
|
||||
|
||||
## Initial Setup
|
||||
|
||||
See [references/anytype-setup.md](references/anytype-setup.md) for:
|
||||
- Step-by-step Anytype space creation
|
||||
- Type and property configuration
|
||||
- Initial Area objects to create
|
||||
- View setup recommendations
|
||||
```dataview
|
||||
TASK
|
||||
WHERE !completed AND due < date(today)
|
||||
SORT due ASC
|
||||
GROUP BY project
|
||||
```
|
||||
|
||||
@@ -1,176 +0,0 @@
|
||||
# Anytype Space Setup Guide
|
||||
|
||||
Manual setup for the Chiron space in Anytype.
|
||||
|
||||
## Step 1: Create Space
|
||||
|
||||
1. Open Anytype desktop app
|
||||
2. Click **+** to create new space
|
||||
3. Name: **Chiron**
|
||||
4. Description: *Personal AI Assistant workspace using PARA methodology*
|
||||
|
||||
## Step 2: Create Types
|
||||
|
||||
Create these object types in the Chiron space:
|
||||
|
||||
### Area Type
|
||||
- **Name**: Area
|
||||
- **Plural**: Areas
|
||||
- **Layout**: Basic
|
||||
- **Icon**: Briefcase (blue)
|
||||
|
||||
### Project Type
|
||||
- **Name**: Project
|
||||
- **Plural**: Projects
|
||||
- **Layout**: Basic
|
||||
- **Icon**: Rocket (purple)
|
||||
|
||||
### Task Type
|
||||
- **Name**: Task
|
||||
- **Plural**: Tasks
|
||||
- **Layout**: Action (checkbox)
|
||||
- **Icon**: Checkbox (blue)
|
||||
|
||||
### Resource Type
|
||||
- **Name**: Resource
|
||||
- **Plural**: Resources
|
||||
- **Layout**: Basic
|
||||
- **Icon**: Book (teal)
|
||||
|
||||
## Step 3: Create Properties
|
||||
|
||||
Add these properties (relations) to the space:
|
||||
|
||||
### Status (Select)
|
||||
| Tag | Color |
|
||||
|-----|-------|
|
||||
| Inbox | Grey |
|
||||
| Next | Blue |
|
||||
| Waiting | Yellow |
|
||||
| Scheduled | Purple |
|
||||
| Done | Lime |
|
||||
|
||||
### Priority (Select)
|
||||
| Tag | Color |
|
||||
|-----|-------|
|
||||
| Critical | Red |
|
||||
| High | Orange |
|
||||
| Medium | Yellow |
|
||||
| Low | Grey |
|
||||
|
||||
### Energy (Select)
|
||||
| Tag | Color |
|
||||
|-----|-------|
|
||||
| High | Red |
|
||||
| Medium | Yellow |
|
||||
| Low | Blue |
|
||||
|
||||
### Context (Multi-select)
|
||||
| Tag | Color |
|
||||
|-----|-------|
|
||||
| Deep Work | Purple |
|
||||
| Admin | Grey |
|
||||
| Calls | Blue |
|
||||
| Errands | Teal |
|
||||
| Quick Wins | Lime |
|
||||
|
||||
### Other Properties
|
||||
- **Area** (Relation → Area type)
|
||||
- **Project** (Relation → Project type)
|
||||
- **Due Date** (Date)
|
||||
- **Outcome** (Text)
|
||||
- **Description** (Text)
|
||||
|
||||
## Step 4: Link Properties to Types
|
||||
|
||||
### Task Type Properties
|
||||
- Status
|
||||
- Priority
|
||||
- Energy
|
||||
- Context
|
||||
- Area (relation)
|
||||
- Project (relation)
|
||||
- Due Date
|
||||
|
||||
### Project Type Properties
|
||||
- Status
|
||||
- Priority
|
||||
- Area (relation)
|
||||
- Due Date
|
||||
- Outcome
|
||||
|
||||
### Area Type Properties
|
||||
- Description
|
||||
|
||||
## Step 5: Create Initial Areas
|
||||
|
||||
Create these Area objects:
|
||||
|
||||
1. **CTO Leadership**
|
||||
- Description: Team management, technical strategy, architecture decisions, hiring
|
||||
|
||||
2. **m3ta.dev**
|
||||
- Description: Content creation, courses, coaching, tutoring programs
|
||||
|
||||
3. **YouTube @m3tam3re**
|
||||
- Description: Technical exploration videos, tutorials, self-hosting guides
|
||||
|
||||
4. **Technical Exploration**
|
||||
- Description: NixOS, self-hosting, AI agents, automation experiments
|
||||
|
||||
5. **Personal Development**
|
||||
- Description: Learning, skills growth, reading
|
||||
|
||||
6. **Health & Wellness**
|
||||
- Description: Exercise, rest, sustainability
|
||||
|
||||
7. **Family**
|
||||
- Description: Quality time, responsibilities
|
||||
|
||||
## Step 6: Create Views (Optional)
|
||||
|
||||
Create these Set views for quick access:
|
||||
|
||||
### Inbox View
|
||||
- Filter: Status = Inbox
|
||||
- Sort: Created date (newest)
|
||||
|
||||
### Today's Focus
|
||||
- Filter: Status = Next AND Due Date <= Today
|
||||
- Sort: Priority (Critical first)
|
||||
|
||||
### By Area
|
||||
- Group by: Area relation
|
||||
- Filter: Status != Done
|
||||
|
||||
### Weekly Review
|
||||
- Filter: Status != Done
|
||||
- Group by: Area
|
||||
- Sort: Due Date
|
||||
|
||||
## Step 7: API Setup (For Automation)
|
||||
|
||||
To enable API access for Chiron agent:
|
||||
|
||||
1. Go to Anytype settings
|
||||
2. Find API/Integration settings
|
||||
3. Generate API key
|
||||
4. Configure in your environment or MCP settings
|
||||
|
||||
Without API access, use manual workflows or n8n integration.
|
||||
|
||||
## Verification
|
||||
|
||||
After setup, you should have:
|
||||
- [ ] Chiron space created
|
||||
- [ ] 4 custom types (Area, Project, Task, Resource)
|
||||
- [ ] 4 select properties (Status, Priority, Energy, Context)
|
||||
- [ ] 3 relation properties (Area, Project, Due Date)
|
||||
- [ ] 7 Area objects created
|
||||
- [ ] At least one view configured
|
||||
|
||||
## Notes
|
||||
|
||||
- The Note type is built-in, use it for quick captures
|
||||
- Archive can be a status tag or separate type (your preference)
|
||||
- Adjust colors and icons to your preference
|
||||
@@ -1,346 +0,0 @@
|
||||
# Anytype API Workflows
|
||||
|
||||
API patterns for task management operations in the Chiron space.
|
||||
|
||||
## Setup
|
||||
|
||||
### Space Configuration
|
||||
|
||||
**Space Name**: Chiron
|
||||
**Space ID**: Retrieve via `Anytype_API-list-spaces` after creation
|
||||
|
||||
```
|
||||
# List spaces to find Chiron space ID
|
||||
Anytype_API-list-spaces
|
||||
|
||||
# Store space_id for subsequent calls
|
||||
SPACE_ID="<chiron-space-id>"
|
||||
```
|
||||
|
||||
### Required Types
|
||||
|
||||
Create these types if they don't exist:
|
||||
|
||||
#### Area Type
|
||||
```
|
||||
Anytype_API-create-type
|
||||
space_id: SPACE_ID
|
||||
name: "Area"
|
||||
plural_name: "Areas"
|
||||
layout: "basic"
|
||||
key: "area"
|
||||
properties:
|
||||
- name: "Description", key: "description", format: "text"
|
||||
- name: "Review Frequency", key: "review_frequency", format: "select"
|
||||
```
|
||||
|
||||
#### Project Type
|
||||
```
|
||||
Anytype_API-create-type
|
||||
space_id: SPACE_ID
|
||||
name: "Project"
|
||||
plural_name: "Projects"
|
||||
layout: "basic"
|
||||
key: "project"
|
||||
properties:
|
||||
- name: "Status", key: "status", format: "select"
|
||||
- name: "Priority", key: "priority", format: "select"
|
||||
- name: "Area", key: "area", format: "objects"
|
||||
- name: "Due Date", key: "due_date", format: "date"
|
||||
- name: "Outcome", key: "outcome", format: "text"
|
||||
```
|
||||
|
||||
#### Task Type
|
||||
```
|
||||
Anytype_API-create-type
|
||||
space_id: SPACE_ID
|
||||
name: "Task"
|
||||
plural_name: "Tasks"
|
||||
layout: "action"
|
||||
key: "task"
|
||||
properties:
|
||||
- name: "Status", key: "status", format: "select"
|
||||
- name: "Priority", key: "priority", format: "select"
|
||||
- name: "Area", key: "area", format: "objects"
|
||||
- name: "Project", key: "project", format: "objects"
|
||||
- name: "Due Date", key: "due_date", format: "date"
|
||||
- name: "Energy", key: "energy", format: "select"
|
||||
- name: "Context", key: "context", format: "multi_select"
|
||||
```
|
||||
|
||||
### Required Properties with Tags
|
||||
|
||||
#### Status Property Tags
|
||||
```
|
||||
Anytype_API-create-property
|
||||
space_id: SPACE_ID
|
||||
name: "Status"
|
||||
key: "status"
|
||||
format: "select"
|
||||
tags:
|
||||
- name: "Inbox", color: "grey"
|
||||
- name: "Next", color: "blue"
|
||||
- name: "Waiting", color: "yellow"
|
||||
- name: "Scheduled", color: "purple"
|
||||
- name: "Done", color: "lime"
|
||||
```
|
||||
|
||||
#### Priority Property Tags
|
||||
```
|
||||
Anytype_API-create-property
|
||||
space_id: SPACE_ID
|
||||
name: "Priority"
|
||||
key: "priority"
|
||||
format: "select"
|
||||
tags:
|
||||
- name: "Critical", color: "red"
|
||||
- name: "High", color: "orange"
|
||||
- name: "Medium", color: "yellow"
|
||||
- name: "Low", color: "grey"
|
||||
```
|
||||
|
||||
#### Energy Property Tags
|
||||
```
|
||||
Anytype_API-create-property
|
||||
space_id: SPACE_ID
|
||||
name: "Energy"
|
||||
key: "energy"
|
||||
format: "select"
|
||||
tags:
|
||||
- name: "High", color: "red"
|
||||
- name: "Medium", color: "yellow"
|
||||
- name: "Low", color: "blue"
|
||||
```
|
||||
|
||||
#### Context Property Tags
|
||||
```
|
||||
Anytype_API-create-property
|
||||
space_id: SPACE_ID
|
||||
name: "Context"
|
||||
key: "context"
|
||||
format: "multi_select"
|
||||
tags:
|
||||
- name: "Deep Work", color: "purple"
|
||||
- name: "Admin", color: "grey"
|
||||
- name: "Calls", color: "blue"
|
||||
- name: "Errands", color: "teal"
|
||||
- name: "Quick Wins", color: "lime"
|
||||
```
|
||||
|
||||
## CRUD Operations
|
||||
|
||||
### Create Task
|
||||
|
||||
```
|
||||
Anytype_API-create-object
|
||||
space_id: SPACE_ID
|
||||
type_key: "task"
|
||||
name: "Task title here"
|
||||
body: "Optional task description or notes"
|
||||
properties:
|
||||
- key: "status", select: "<status_tag_id>"
|
||||
- key: "priority", select: "<priority_tag_id>"
|
||||
- key: "area", objects: ["<area_object_id>"]
|
||||
- key: "due_date", date: "2025-01-10"
|
||||
icon:
|
||||
format: "icon"
|
||||
name: "checkbox"
|
||||
color: "blue"
|
||||
```
|
||||
|
||||
### Create Project
|
||||
|
||||
```
|
||||
Anytype_API-create-object
|
||||
space_id: SPACE_ID
|
||||
type_key: "project"
|
||||
name: "Project title"
|
||||
body: "Project description and goals"
|
||||
properties:
|
||||
- key: "status", select: "<active_tag_id>"
|
||||
- key: "area", objects: ["<area_object_id>"]
|
||||
- key: "outcome", text: "What done looks like"
|
||||
icon:
|
||||
format: "icon"
|
||||
name: "rocket"
|
||||
color: "purple"
|
||||
```
|
||||
|
||||
### Create Area
|
||||
|
||||
```
|
||||
Anytype_API-create-object
|
||||
space_id: SPACE_ID
|
||||
type_key: "area"
|
||||
name: "CTO Leadership"
|
||||
body: "Team management, technical strategy, architecture decisions"
|
||||
properties:
|
||||
- key: "description", text: "Standards: Team health, technical excellence, strategic alignment"
|
||||
- key: "review_frequency", select: "<weekly_tag_id>"
|
||||
icon:
|
||||
format: "icon"
|
||||
name: "briefcase"
|
||||
color: "blue"
|
||||
```
|
||||
|
||||
### Quick Capture (Inbox)
|
||||
|
||||
```
|
||||
Anytype_API-create-object
|
||||
space_id: SPACE_ID
|
||||
type_key: "note"
|
||||
name: "Quick capture content here"
|
||||
properties:
|
||||
- key: "status", select: "<inbox_tag_id>"
|
||||
icon:
|
||||
format: "icon"
|
||||
name: "mail"
|
||||
color: "grey"
|
||||
```
|
||||
|
||||
### Update Task Status
|
||||
|
||||
```
|
||||
Anytype_API-update-object
|
||||
space_id: SPACE_ID
|
||||
object_id: "<task_object_id>"
|
||||
properties:
|
||||
- key: "status", select: "<done_tag_id>"
|
||||
```
|
||||
|
||||
## Query Patterns
|
||||
|
||||
### Get All Tasks for Today
|
||||
|
||||
```
|
||||
Anytype_API-search-space
|
||||
space_id: SPACE_ID
|
||||
types: ["task"]
|
||||
filters:
|
||||
operator: "and"
|
||||
conditions:
|
||||
- property_key: "status"
|
||||
select: "<next_tag_id>"
|
||||
- property_key: "due_date"
|
||||
date: "2025-01-05"
|
||||
condition: "le"
|
||||
```
|
||||
|
||||
### Get Inbox Items
|
||||
|
||||
```
|
||||
Anytype_API-search-space
|
||||
space_id: SPACE_ID
|
||||
filters:
|
||||
operator: "and"
|
||||
conditions:
|
||||
- property_key: "status"
|
||||
select: "<inbox_tag_id>"
|
||||
sort:
|
||||
property_key: "created_date"
|
||||
direction: "desc"
|
||||
```
|
||||
|
||||
### Get Tasks by Area
|
||||
|
||||
```
|
||||
Anytype_API-search-space
|
||||
space_id: SPACE_ID
|
||||
types: ["task"]
|
||||
filters:
|
||||
operator: "and"
|
||||
conditions:
|
||||
- property_key: "area"
|
||||
objects: ["<area_object_id>"]
|
||||
- property_key: "status"
|
||||
condition: "nempty"
|
||||
```
|
||||
|
||||
### Get Active Projects
|
||||
|
||||
```
|
||||
Anytype_API-search-space
|
||||
space_id: SPACE_ID
|
||||
types: ["project"]
|
||||
filters:
|
||||
conditions:
|
||||
- property_key: "status"
|
||||
select: "<active_tag_id>"
|
||||
```
|
||||
|
||||
### Get Overdue Tasks
|
||||
|
||||
```
|
||||
Anytype_API-search-space
|
||||
space_id: SPACE_ID
|
||||
types: ["task"]
|
||||
filters:
|
||||
operator: "and"
|
||||
conditions:
|
||||
- property_key: "due_date"
|
||||
date: "<today>"
|
||||
condition: "lt"
|
||||
- property_key: "status"
|
||||
condition: "nempty"
|
||||
```
|
||||
|
||||
### Get Tasks by Context
|
||||
|
||||
```
|
||||
Anytype_API-search-space
|
||||
space_id: SPACE_ID
|
||||
types: ["task"]
|
||||
filters:
|
||||
conditions:
|
||||
- property_key: "context"
|
||||
multi_select: ["<deep_work_tag_id>"]
|
||||
- property_key: "status"
|
||||
select: "<next_tag_id>"
|
||||
```
|
||||
|
||||
## Batch Operations
|
||||
|
||||
### Complete Multiple Tasks
|
||||
|
||||
```python
|
||||
# Pseudocode for batch completion
|
||||
task_ids = ["id1", "id2", "id3"]
|
||||
done_tag_id = "<done_tag_id>"
|
||||
|
||||
for task_id in task_ids:
|
||||
Anytype_API-update-object(
|
||||
space_id=SPACE_ID,
|
||||
object_id=task_id,
|
||||
properties=[{"key": "status", "select": done_tag_id}]
|
||||
)
|
||||
```
|
||||
|
||||
### Archive Completed Projects
|
||||
|
||||
```
|
||||
# 1. Find completed projects
|
||||
Anytype_API-search-space
|
||||
space_id: SPACE_ID
|
||||
types: ["project"]
|
||||
filters:
|
||||
conditions:
|
||||
- property_key: "status"
|
||||
select: "<completed_tag_id>"
|
||||
|
||||
# 2. For each, update to archived status or move to archive
|
||||
```
|
||||
|
||||
## Error Handling
|
||||
|
||||
| Error | Cause | Solution |
|
||||
|-------|-------|----------|
|
||||
| 401 Unauthorized | Missing/invalid auth | Check API key configuration |
|
||||
| 404 Not Found | Invalid space/object ID | Verify IDs with list operations |
|
||||
| 400 Bad Request | Invalid property format | Check property types match expected format |
|
||||
|
||||
## Notes
|
||||
|
||||
- Always retrieve space_id fresh via `list-spaces` before operations
|
||||
- Tag IDs must be retrieved via `list-tags` for the specific property
|
||||
- Object relations require the target object's ID, not name
|
||||
- Dates use ISO 8601 format: `2025-01-05` or `2025-01-05T18:00:00Z`
|
||||
@@ -1,190 +0,0 @@
|
||||
# PARA Methodology Reference
|
||||
|
||||
PARA is a universal system for organizing digital information, created by Tiago Forte.
|
||||
|
||||
## The Four Categories
|
||||
|
||||
### Projects
|
||||
|
||||
**Definition**: A series of tasks linked to a goal, with a deadline.
|
||||
|
||||
**Characteristics**:
|
||||
- Has a clear outcome/deliverable
|
||||
- Has a deadline (explicit or implicit)
|
||||
- Requires multiple tasks to complete
|
||||
- Can be completed (finite)
|
||||
|
||||
**Examples**:
|
||||
- Launch NixOS Flakes course
|
||||
- Hire senior backend developer
|
||||
- Complete Q1 board presentation
|
||||
- Publish self-hosting playbook video
|
||||
|
||||
**Questions to identify**:
|
||||
- What am I committed to finishing?
|
||||
- What has a deadline?
|
||||
- What would I celebrate completing?
|
||||
|
||||
### Areas
|
||||
|
||||
**Definition**: A sphere of activity with a standard to be maintained over time.
|
||||
|
||||
**Characteristics**:
|
||||
- Ongoing responsibility (infinite)
|
||||
- Has standards, not deadlines
|
||||
- Requires regular attention
|
||||
- Never "complete" - only maintained
|
||||
|
||||
**Sascha's Areas**:
|
||||
1. CTO Leadership
|
||||
2. m3ta.dev
|
||||
3. YouTube @m3tam3re
|
||||
4. Technical Exploration
|
||||
5. Personal Development
|
||||
6. Health & Wellness
|
||||
7. Family
|
||||
|
||||
**Questions to identify**:
|
||||
- What roles do I maintain?
|
||||
- What standards must I uphold?
|
||||
- What would suffer if I ignored it?
|
||||
|
||||
### Resources
|
||||
|
||||
**Definition**: A topic or theme of ongoing interest.
|
||||
|
||||
**Characteristics**:
|
||||
- Reference material for future use
|
||||
- No immediate action required
|
||||
- Supports projects and areas
|
||||
- Can be shared or reused
|
||||
|
||||
**Examples**:
|
||||
- NixOS configuration patterns
|
||||
- n8n workflow templates
|
||||
- Self-hosting architecture docs
|
||||
- AI prompt libraries
|
||||
- Book notes and highlights
|
||||
|
||||
**Questions to identify**:
|
||||
- What might be useful later?
|
||||
- What do I want to learn more about?
|
||||
- What reference material do I need?
|
||||
|
||||
### Archives
|
||||
|
||||
**Definition**: Inactive items from the other three categories.
|
||||
|
||||
**Characteristics**:
|
||||
- Completed projects
|
||||
- Areas no longer active
|
||||
- Resources no longer relevant
|
||||
- Preserved for reference, not action
|
||||
|
||||
**When to archive**:
|
||||
- Project completed or cancelled
|
||||
- Role/responsibility ended
|
||||
- Topic no longer relevant
|
||||
- Information outdated
|
||||
|
||||
## The PARA Workflow
|
||||
|
||||
### Capture
|
||||
Everything starts in the **Inbox**. Don't organize during capture.
|
||||
|
||||
### Clarify
|
||||
Ask: "Is this actionable?"
|
||||
- **Yes** → Is it a single task or a project?
|
||||
- **No** → Is it reference material or trash?
|
||||
|
||||
### Organize
|
||||
Place items in the appropriate category:
|
||||
- Active work → Projects (linked to Area)
|
||||
- Ongoing standards → Areas
|
||||
- Reference → Resources
|
||||
- Done/irrelevant → Archives
|
||||
|
||||
### Review
|
||||
- **Daily**: Process inbox, check today's tasks
|
||||
- **Weekly**: Review all projects, check areas, process resources
|
||||
- **Monthly**: Archive completed, assess areas, audit resources
|
||||
|
||||
## Project vs Area Confusion
|
||||
|
||||
The most common PARA mistake is confusing projects and areas.
|
||||
|
||||
| If you treat a Project as an Area | If you treat an Area as a Project |
|
||||
|-----------------------------------|-----------------------------------|
|
||||
| Never feels "done" | Feels like constant failure |
|
||||
| Scope creeps infinitely | Standards slip without noticing |
|
||||
| No sense of progress | Burnout from "finishing" the infinite |
|
||||
|
||||
**Test**: Can I complete this in a single work session series?
|
||||
- Yes → Project
|
||||
- No, it's ongoing → Area
|
||||
|
||||
## Maintenance Rhythms
|
||||
|
||||
### Daily (Evening - 10 min)
|
||||
1. Process inbox items
|
||||
2. Review completed tasks
|
||||
3. Set tomorrow's priorities
|
||||
|
||||
### Weekly (Sunday evening - 30 min)
|
||||
1. Get clear: Inbox to zero
|
||||
2. Get current: Review each Area
|
||||
3. Review all active Projects
|
||||
4. Plan next week's outcomes
|
||||
|
||||
### Monthly (First Sunday - 60 min)
|
||||
1. Review Area standards
|
||||
2. Archive completed Projects
|
||||
3. Evaluate stalled Projects
|
||||
4. Audit Resources relevance
|
||||
|
||||
### Quarterly (90 min)
|
||||
1. Review life Areas balance
|
||||
2. Set quarterly outcomes
|
||||
3. Major archives cleanup
|
||||
4. System improvements
|
||||
|
||||
## PARA in Anytype
|
||||
|
||||
### Type Mapping
|
||||
|
||||
| PARA | Anytype Type | Notes |
|
||||
|------|--------------|-------|
|
||||
| Project | `project` | Has area relation, deadline |
|
||||
| Area | `area` | Top-level organization |
|
||||
| Resource | `resource` | Reference material |
|
||||
| Archive | Use `archived` property | Or separate Archive type |
|
||||
| Task | `task` | Lives within Project or Area |
|
||||
| Inbox | `note` with status=inbox | Quick capture |
|
||||
|
||||
### Recommended Properties
|
||||
|
||||
**On Projects**:
|
||||
- `area` (relation) - Which area owns this
|
||||
- `status` (select) - active, on-hold, completed
|
||||
- `due_date` (date) - Target completion
|
||||
- `outcome` (text) - What does "done" look like
|
||||
|
||||
**On Tasks**:
|
||||
- `project` or `area` (relation) - Parent container
|
||||
- `status` (select) - inbox, next, waiting, scheduled, done
|
||||
- `priority` (select) - critical, high, medium, low
|
||||
- `due_date` (date) - When it's needed
|
||||
- `energy` (select) - Required energy level
|
||||
- `context` (multi_select) - Where/how it can be done
|
||||
|
||||
**On Areas**:
|
||||
- `description` (text) - Standards to maintain
|
||||
- `review_frequency` (select) - daily, weekly, monthly
|
||||
|
||||
## Common Pitfalls
|
||||
|
||||
1. **Over-organizing during capture** - Just dump it in inbox
|
||||
2. **Too many projects** - Active projects should be <15
|
||||
3. **Orphan tasks** - Every task needs a project or area
|
||||
4. **Stale resources** - Archive what you haven't touched in 6 months
|
||||
5. **Skipping reviews** - The system only works if you review it
|
||||
@@ -1,307 +0,0 @@
|
||||
# Review Templates
|
||||
|
||||
Structured templates for daily and weekly reviews.
|
||||
|
||||
## Daily Review Template (Evening)
|
||||
|
||||
**Duration**: 10-15 minutes
|
||||
**Best time**: Evening, after work concludes
|
||||
|
||||
### Script
|
||||
|
||||
```
|
||||
## Daily Review - [DATE]
|
||||
|
||||
### Wins Today
|
||||
[List completed tasks - celebrate progress]
|
||||
|
||||
- [x]
|
||||
- [x]
|
||||
- [x]
|
||||
|
||||
### Still Open
|
||||
[Tasks started but not finished]
|
||||
|
||||
- [ ] [Task] - [Status/blocker]
|
||||
- [ ] [Task] - [Rescheduled to: DATE]
|
||||
|
||||
### Inbox Check
|
||||
- Items in inbox: [COUNT]
|
||||
- Quick processing:
|
||||
- [Item] → [Action: task/project/trash/defer]
|
||||
|
||||
### Energy Assessment
|
||||
- How was today's energy? [High/Medium/Low]
|
||||
- What drained energy?
|
||||
- What boosted energy?
|
||||
|
||||
### Tomorrow's Top 3
|
||||
[Most impactful tasks for tomorrow - set before sleeping]
|
||||
|
||||
1. **[TASK]** - Why: [impact reason]
|
||||
2. **[TASK]** - Why: [impact reason]
|
||||
3. **[TASK]** - Why: [impact reason]
|
||||
|
||||
### Blockers to Address
|
||||
- [Blocker] - Need: [what's needed to unblock]
|
||||
|
||||
### Notes for Tomorrow
|
||||
[Anything to remember, context to preserve]
|
||||
|
||||
---
|
||||
Review completed at: [TIME]
|
||||
```
|
||||
|
||||
### Daily Review Checklist
|
||||
|
||||
- [ ] Review calendar for tomorrow
|
||||
- [ ] Check completed tasks
|
||||
- [ ] Process any urgent inbox items
|
||||
- [ ] Identify top 3 priorities
|
||||
- [ ] Note any blockers
|
||||
- [ ] Clear desk/workspace (physical reset)
|
||||
|
||||
## Weekly Review Template
|
||||
|
||||
**Duration**: 30-45 minutes
|
||||
**Best time**: Sunday evening or Friday afternoon
|
||||
|
||||
### Script
|
||||
|
||||
```
|
||||
## Weekly Review - Week of [DATE]
|
||||
|
||||
### Part 1: Get Clear (Capture)
|
||||
|
||||
#### Inbox Processing
|
||||
- Starting inbox count: [COUNT]
|
||||
- Process each item:
|
||||
- [Item] → [Destination: project/area/resource/trash]
|
||||
- Ending inbox count: [TARGET: 0]
|
||||
|
||||
#### Loose Ends
|
||||
- Notes to process:
|
||||
- Voice memos:
|
||||
- Screenshots/photos:
|
||||
- Browser tabs to close:
|
||||
- Email to archive:
|
||||
|
||||
### Part 2: Get Current (Review)
|
||||
|
||||
#### Area Review
|
||||
|
||||
**CTO Leadership**
|
||||
- Active projects: [list]
|
||||
- Stalled items: [list]
|
||||
- Standards check: [On track / Needs attention]
|
||||
- Next week focus:
|
||||
|
||||
**m3ta.dev**
|
||||
- Active projects: [list]
|
||||
- Content pipeline:
|
||||
- Next week focus:
|
||||
|
||||
**YouTube @m3tam3re**
|
||||
- Active projects: [list]
|
||||
- Upload schedule:
|
||||
- Next week focus:
|
||||
|
||||
**Technical Exploration**
|
||||
- Current experiments:
|
||||
- Learning goals:
|
||||
- Next week focus:
|
||||
|
||||
**Personal Development**
|
||||
- Current focus:
|
||||
- Progress:
|
||||
- Next week focus:
|
||||
|
||||
**Health & Wellness**
|
||||
- This week: [assessment]
|
||||
- Next week intention:
|
||||
|
||||
**Family**
|
||||
- Quality time this week:
|
||||
- Next week plans:
|
||||
|
||||
#### Project Status
|
||||
|
||||
| Project | Area | Status | Next Action | Due |
|
||||
|---------|------|--------|-------------|-----|
|
||||
| [Name] | [Area] | [On track/Stalled/Blocked] | [Next step] | [Date] |
|
||||
|
||||
#### Waiting For
|
||||
[Items waiting on others]
|
||||
|
||||
| Item | Waiting On | Since | Follow-up Date |
|
||||
|------|-----------|-------|----------------|
|
||||
| | | | |
|
||||
|
||||
### Part 3: Get Creative (Reflect)
|
||||
|
||||
#### What Worked This Week?
|
||||
-
|
||||
|
||||
#### What Didn't Work?
|
||||
-
|
||||
|
||||
#### New Ideas/Projects
|
||||
[Don't commit yet - just capture]
|
||||
-
|
||||
|
||||
#### Should I Start?
|
||||
[New projects to consider]
|
||||
-
|
||||
|
||||
#### Should I Stop?
|
||||
[Projects or commitments to drop]
|
||||
-
|
||||
|
||||
#### Should I Continue?
|
||||
[Projects going well]
|
||||
-
|
||||
|
||||
### Part 4: Plan Next Week
|
||||
|
||||
#### Weekly Outcomes
|
||||
[3-5 specific outcomes for the week]
|
||||
|
||||
1. [ ]
|
||||
2. [ ]
|
||||
3. [ ]
|
||||
4. [ ]
|
||||
5. [ ]
|
||||
|
||||
#### Time Blocks
|
||||
[Protect time for deep work]
|
||||
|
||||
| Day | Block | Focus |
|
||||
|-----|-------|-------|
|
||||
| Mon | | |
|
||||
| Tue | | |
|
||||
| Wed | | |
|
||||
| Thu | | |
|
||||
| Fri | | |
|
||||
|
||||
#### Key Meetings
|
||||
-
|
||||
|
||||
#### Week Theme (Optional)
|
||||
[One word or phrase to guide the week]
|
||||
|
||||
---
|
||||
Review completed at: [TIME]
|
||||
Next weekly review: [DATE]
|
||||
```
|
||||
|
||||
### Weekly Review Checklist
|
||||
|
||||
- [ ] Close all browser tabs
|
||||
- [ ] Process email inbox to zero
|
||||
- [ ] Process Anytype inbox to zero
|
||||
- [ ] Review each Area
|
||||
- [ ] Check all active Projects
|
||||
- [ ] Review Waiting For list
|
||||
- [ ] Clear completed tasks
|
||||
- [ ] Archive finished projects
|
||||
- [ ] Set weekly outcomes
|
||||
- [ ] Block deep work time
|
||||
- [ ] Review calendar for the week
|
||||
|
||||
## Monthly Review Template
|
||||
|
||||
**Duration**: 60 minutes
|
||||
**Best time**: First Sunday of the month
|
||||
|
||||
### Script
|
||||
|
||||
```
|
||||
## Monthly Review - [MONTH YEAR]
|
||||
|
||||
### Month Metrics
|
||||
- Projects completed: [COUNT]
|
||||
- Projects started: [COUNT]
|
||||
- Tasks completed: [COUNT]
|
||||
- Inbox avg items: [COUNT]
|
||||
|
||||
### Area Deep Dive
|
||||
|
||||
[For each Area, rate 1-10 and note]
|
||||
|
||||
| Area | Rating | Notes | Action |
|
||||
|------|--------|-------|--------|
|
||||
| CTO Leadership | /10 | | |
|
||||
| m3ta.dev | /10 | | |
|
||||
| YouTube | /10 | | |
|
||||
| Tech Exploration | /10 | | |
|
||||
| Personal Dev | /10 | | |
|
||||
| Health | /10 | | |
|
||||
| Family | /10 | | |
|
||||
|
||||
### Project Archive
|
||||
[Projects completed this month → Archive]
|
||||
|
||||
-
|
||||
|
||||
### Stalled Projects
|
||||
[No progress in 30+ days - decide: continue, pause, or kill]
|
||||
|
||||
| Project | Days Stalled | Decision |
|
||||
|---------|--------------|----------|
|
||||
| | | |
|
||||
|
||||
### Resource Audit
|
||||
[Resources not accessed in 3+ months - archive or keep?]
|
||||
|
||||
-
|
||||
|
||||
### System Improvements
|
||||
[What's not working in the system?]
|
||||
|
||||
-
|
||||
|
||||
### Next Month Focus
|
||||
[Top 3 priorities for the month]
|
||||
|
||||
1.
|
||||
2.
|
||||
3.
|
||||
|
||||
---
|
||||
Review completed at: [TIME]
|
||||
Next monthly review: [DATE]
|
||||
```
|
||||
|
||||
## ntfy Notification Templates
|
||||
|
||||
### Daily Review Summary
|
||||
```
|
||||
Daily Review Complete
|
||||
|
||||
Completed: [X] tasks
|
||||
Tomorrow's Top 3:
|
||||
1. [Task 1]
|
||||
2. [Task 2]
|
||||
3. [Task 3]
|
||||
|
||||
Inbox: [X] items pending
|
||||
```
|
||||
|
||||
### Weekly Review Reminder
|
||||
```
|
||||
Weekly Review Reminder
|
||||
|
||||
Time for your weekly review!
|
||||
Start here: "weekly review"
|
||||
```
|
||||
|
||||
### Overdue Alert
|
||||
```
|
||||
Overdue Tasks Alert
|
||||
|
||||
[X] tasks past due date:
|
||||
- [Task 1] (due [DATE])
|
||||
- [Task 2] (due [DATE])
|
||||
|
||||
Review now: "show overdue"
|
||||
```
|
||||
Reference in New Issue
Block a user