Update Obsidian vault path from ~/knowledge to ~/CODEX

commands/chiron-capture.md

@@ -0,0 +1,34 @@
+---
+name: /chiron-capture
+description: "Quick capture to inbox - minimal friction capture for tasks, notes, meetings, learnings"
+---
+
+# Quick Capture
+
+Instant capture to inbox for later processing.
+
+## Steps
+
+1. **Parse capture type** from request:
+   - Task → Create in `~/CODEX/tasks/inbox.md`
+   - Note → Create in `~/CODEX/00-inbox/quick-capture-*.md`
+   - Meeting → Create in `~/CODEX/00-inbox/meetings/meeting-*.md`
+   - Learning → Create in `~/CODEX/00-inbox/learnings/learning-*.md`
+   - Reference → Create in `~/CODEX/00-inbox/web-clips/*.md`
+2. **Use appropriate format** (Obsidian Tasks format for tasks, markdown with frontmatter for notes)
+3. **Add minimal metadata** (creation date, tags from context)
+4. **Confirm capture**
+
+## Expected Output
+
+Appropriate file created in inbox with:
+- Tasks in Obsidian Tasks format: `- [ ] Task #tag ⏫ 📅 date`
+- Notes with frontmatter and timestamped content
+- Quick confirmation: "Captured to inbox. Process during weekly review."
+
+## Related Skills
+
+- `quick-capture` - Core capture workflows for all types
+- `obsidian-management` - File creation in inbox structure
+- `task-management` - Task format and placement
+- `meeting-notes` - Meeting note templates

commands/chiron-end.md

@@ -0,0 +1,35 @@
+---
+name: /chiron-end
+description: "Evening reflection ritual - review the day, capture wins/learnings, plan tomorrow"
+---
+
+# Evening Reflection
+
+Close the day with gratitude and preparation for tomorrow.
+
+## Steps
+
+1. **Review completed tasks** from today's daily note
+2. **Capture key wins** (top 3)
+3. **Identify challenges and blockers**
+4. **Capture learnings** from the day
+5. **Plan tomorrow's focus** (carry over incomplete tasks, identify top priorities)
+6. **Ask reflection question** (see `chiron-core` references/reflection-questions.md)
+
+## Expected Output
+
+Updated daily note with:
+- Completed tasks (marked off)
+- Wins section
+- Challenges section
+- Learnings section
+- Tomorrow's focus
+- Energy level assessment
+- Reflection response
+
+## Related Skills
+
+- `daily-routines` - Core evening reflection workflow
+- `task-management` - Task status updates
+- `chiron-core` - Reflection questions and mentorship
+- `obsidian-management` - Daily note update

commands/chiron-learn.md

@@ -0,0 +1,41 @@
+---
+name: /chiron-learn
+description: "Capture learning - record insights, discoveries, and knowledge"
+---
+
+# Capture Learning
+
+Capture learnings and insights for the knowledge base.
+
+## Steps
+
+1. **Parse learning request**:
+   - Topic (if short)
+   - Content (if long description provided)
+2. **If topic provided**:
+   - Search for existing notes on this topic in `~/CODEX/03-resources/`
+   - Present what's already captured
+   - Ask if user wants to add to existing or create new
+3. **Create learning note**:
+   - Location: `~/CODEX/03-resources/[topic]/[topic].md`
+   - Or `~/CODEX/00-inbox/learnings/learning-[topic]-YYYYMMDD.md` (if quick capture)
+   - Use frontmatter with tags `#learning` and topic
+   - Include: what was learned, context, applications
+4. **Link to related notes** (find and wiki-link)
+5. **Confirm** creation
+
+## Expected Output
+
+Learning note created with:
+- Proper frontmatter (tags, created date, topic)
+- What was learned
+- Context or source
+- Applications or how to use this knowledge
+- Links to related notes
+- Confirmation of creation
+
+## Related Skills
+
+- `quick-capture` - Quick capture workflow
+- `chiron-core` - PARA methodology for resource placement
+- `obsidian-management` - File operations and linking

commands/chiron-meeting.md

@@ -0,0 +1,43 @@
+---
+name: /chiron-meeting
+description: "Meeting notes - structured capture of meetings with action items"
+---
+
+# Meeting Notes
+
+Take structured meeting notes with action item extraction.
+
+## Steps
+
+1. **Parse meeting request**:
+   - Meeting title (if provided)
+   - Attendees (if mentioned)
+   - Meeting type (standup, 1:1, workshop, decision)
+2. **Create meeting note** using template from `~/CODEX/_chiron/templates/meeting.md`:
+   - Location: `~/CODEX/01-projects/[project]/meetings/[topic]-YYYYMMDD.md` (if project-specific)
+   - Or `~/CODEX/00-inbox/meetings/[topic]-YYYYMMDD.md` (if general)
+3. **Fill in sections**:
+   - Title, date, time, location
+   - Attendees and roles
+   - Notes (if user provides or if meeting in progress)
+   - Decisions made
+   - Action items (extract from notes or user-provided)
+4. **Create action item tasks** in Obsidian Tasks format with owners and due dates
+5. **Link to context** (project or area)
+
+## Expected Output
+
+Meeting note created with:
+- Proper frontmatter (date, attendees, tags)
+- Attendees list
+- Notes section
+- Decisions section
+- Action items in Obsidian Tasks format with @mentions and due dates
+- Links to related projects/areas
+
+## Related Skills
+
+- `meeting-notes` - Core meeting workflow and templates
+- `task-management` - Action item extraction and task creation
+- `obsidian-management` - File operations and template usage
+- `project-structures` - Project meeting placement

commands/chiron-project.md

@@ -0,0 +1,41 @@
+---
+name: /chiron-project
+description: "Create new project - initialize project structure using PARA methodology"
+---
+
+# Create Project
+
+Create a new project with proper PARA structure.
+
+## 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** at `~/CODEX/01-projects/[work|personal]/[project-name]/`
+3. **Create subdirectories**: `meetings/`, `decisions/`, `notes/`, `resources/`
+4. **Create _index.md** using template from `~/CODEX/_chiron/templates/project.md`:
+   - Fill in: title, status, deadline, priority, tags, area
+   - Set to `status: active`
+5. **Create initial files**:
+   - `notes/_index.md` - Project notes index
+   - Link to related area if provided
+6. **Confirm** creation and ask if ready to add tasks
+
+## Expected Output
+
+Project directory created with:
+- `_index.md` (main project file with frontmatter)
+- Subdirectories: `meetings/`, `decisions/`, `notes/`, `resources/`
+- Proper PARA structure and frontmatter
+- Links to related areas if applicable
+
+## Related Skills
+
+- `project-structures` - Core project creation workflow
+- `chiron-core` - PARA methodology for project placement
+- `obsidian-management` - File operations and template usage
+- `task-management` - Initial task creation

commands/chiron-review.md

@@ -0,0 +1,46 @@
+---
+name: /chiron-review
+description: "Comprehensive weekly review - metrics, project status, inbox processing, next week planning"
+---
+
+# Weekly Review
+
+Weekly ritual to clear inbox, review progress, and plan the next week.
+
+## Steps
+
+1. **Collect daily notes** for the week (Monday-Sunday)
+2. **Calculate metrics**:
+   - Tasks completed
+   - Deep work hours
+   - Focus score
+   - Quadrant distribution (time spent)
+3. **Review project status** across all projects in `~/CODEX/01-projects/`
+4. **Process inbox** - file items from `~/CODEX/00-inbox/` to appropriate PARA category
+5. **Review area health** in `~/CODEX/02-areas/`
+6. **Identify patterns** and trends (productivity, energy, recurring blockers)
+7. **Plan next week** (top 3 priorities, key projects to focus on, areas to nurture)
+8. **Generate weekly review note** using template
+
+## Expected Output
+
+Weekly review note at `~/CODEX/daily/weekly-reviews/YYYY-W##.md` with:
+- Metrics (tasks completed, deep work hours, focus score, quadrant distribution)
+- Top 3 wins with impact
+- Key challenges with root causes
+- Patterns & insights
+- Project status (completed, on track, behind, stalled)
+- Area health review
+- Inbox status (processed, remaining)
+- Next week priorities (top 3, projects to focus, areas to nurture)
+- New habits/experiments to try
+- Reflection question response
+
+## Related Skills
+
+- `daily-routines` - Core weekly review workflow
+- `task-management` - Task aggregation and status review
+- `chiron-core` - PARA methodology, reflection questions, prioritization guidance
+- `project-structures` - Project status review
+- `quick-capture` - Inbox processing
+- `obsidian-management` - Weekly review note creation using template

commands/chiron-search.md

@@ -0,0 +1,47 @@
+---
+name: /chiron-search
+description: "Search knowledge base - find notes, tasks, or information in ~/CODEX vault"
+---
+
+# Search Knowledge Base
+
+Find information across the Obsidian vault.
+
+## Steps
+
+1. **Parse search intent**:
+   - Task search → Search for `- [ ]` patterns
+   - Tag search → Search for `#tag` patterns
+   - Recent → Search in `~/CODEX/daily/` for recent files
+   - Full-text → General term search
+2. **Execute search** using `rg`:
+   ```bash
+   # Tasks
+   rg "- \\[ \\]" ~/CODEX --type md
+
+   # Tags
+   rg "#work" ~/CODEX --type md
+
+   # Recent
+   rg "term" ~/CODEX/daily --type md
+
+   # Full text
+   rg "search term" ~/CODEX --type md -C 3
+   ```
+3. **Group results** by location (Projects/Areas/Resources/Daily)
+4. **Present** with context and file paths
+5. **Offer follow-up actions** (read note, edit, create task, etc.)
+
+## Expected Output
+
+Search results grouped by:
+- Location (Projects, Areas, Resources, Daily, Tasks)
+- File paths for easy access
+- Context (matching lines with surrounding content)
+- Follow-up action suggestions
+
+## Related Skills
+
+- `obsidian-management` - Vault search operations
+- `task-management` - Task-specific search
+- `chiron-core` - PARA navigation for locating content

commands/chiron-start.md

@@ -0,0 +1,34 @@
+---
+name: /chiron-start
+description: "Morning planning ritual - set focus for the day and prioritize work"
+---
+
+# Morning Planning
+
+Start the day with clarity and intention.
+
+## Steps
+
+1. **Read yesterday's daily note** from `~/CODEX/daily/YYYY/MM/DD/YYYY-MM-DD.md`
+2. **Check today's tasks** in `~/CODEX/tasks/inbox.md` and project files
+3. **Prioritize using energy levels and deadlines** (consult `chiron-core` for PARA guidance)
+4. **Generate today's focus** (3-5 top priorities, deep work blocks, quick wins)
+5. **Ask**: "Ready to start, or need to adjust?"
+
+## Expected Output
+
+Daily note with:
+- Focus areas (top 3 priorities)
+- Deep work blocks (scheduled)
+- Quick wins (<15min)
+- Meetings
+- Carried over tasks
+- Inbox status
+
+## Related Skills
+
+- `daily-routines` - Core morning planning workflow
+- `task-management` - Task extraction and prioritization
+- `chiron-core` - PARA methodology guidance
+- `obsidian-management` - Daily note creation using template
+- `calendar-scheduling` - Calendar integration for time blocking

commands/chiron-task.md

@@ -0,0 +1,42 @@
+---
+name: /chiron-task
+description: "Add task with smart defaults - create task with proper formatting and placement"
+---
+
+# Add Task
+
+Create a task with proper Obsidian Tasks formatting.
+
+## Steps
+
+1. **Parse task details** from request:
+   - Task description
+   - Priority (if specified: critical, high, low)
+   - Due date (if specified)
+   - Context/project/area (if specified)
+   - Owner (if specified: @mention)
+2. **Determine location**:
+   - Project-specific → `~/CODEX/01-projects/[project]/_index.md` or `tasks.md`
+   - Area-specific → `~/CODEX/02-areas/[area].md`
+   - General → `~/CODEX/tasks/inbox.md`
+3. **Create task in Obsidian format**:
+   ```markdown
+   - [ ] Task description #tag [priority] 👤 [@owner] 📅 YYYY-MM-DD
+   ```
+4. **Confirm** with task details and location
+
+## Expected Output
+
+Task created in appropriate location with:
+- Proper Obsidian Tasks format
+- Priority indicator (⏫/🔼/🔽 or none)
+- Due date if specified
+- Owner attribution if specified
+- Link to project/area if applicable
+
+## Related Skills
+
+- `task-management` - Task creation and placement logic
+- `chiron-core` - PARA methodology for task placement
+- `obsidian-management` - File operations
+- `project-structures` - Project task placement