v2.0: Add hooks, agents, skills, rules, and plugin structure

Major modernization to leverage latest Claude Code features:

Plugin Foundation:
- Add .claude-plugin/plugin.json manifest for distribution
- Add .claude/settings.json with permissions and hooks config

Hooks (automatic behaviors):
- SessionStart: Initialize vault environment variables
- PostToolUse: Auto-commit changes after Write/Edit operations

Custom Agents (4):
- note-organizer: Vault organization and link maintenance
- weekly-reviewer: Facilitate weekly review aligned with goals
- goal-aligner: Check daily/weekly alignment with long-term goals
- inbox-processor: GTD-style inbox processing

Skills (3):
- obsidian-vault-ops: Read/write vault files, manage wiki-links
- goal-tracking: Track progress across goal cascade
- daily-workflow: Morning/midday/evening routines

Modular Rules (3):
- markdown-standards: File naming, tags, frontmatter conventions
- productivity-workflow: Goal cascade, daily/weekly planning
- project-management: Project structure and status tracking

Other:
- Add statusline.sh for terminal vault stats display
- Add CLAUDE.local.md.template for personal overrides
- Update CLAUDE.md with new features documentation
- Update all docs with v2.0 features and upgrade guide

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Bill Allred
2025-12-19 18:57:48 -08:00
parent eda01cbe46
commit 78a822a3df
21 changed files with 1643 additions and 159 deletions

View File

@@ -0,0 +1,130 @@
---
name: daily-workflow
description: Morning routine, midday check-in, and evening shutdown workflows. Structure daily planning, task review, and end-of-day reflection. Use for daily productivity routines.
allowed-tools: Read, Write, Edit, Glob, Grep
---
# Daily Workflow Skill
Structured workflows for morning planning, midday check-ins, and evening shutdowns.
## Morning Routine (5-10 minutes)
### Automated Steps
1. Create today's daily note (if not exists)
2. Pull incomplete tasks from yesterday
3. Review weekly goals for today's priority
4. Surface any calendar events or deadlines
### Interactive Prompts
- "What's your ONE thing for today?"
- "What might get in the way?"
- "How do you want to feel at end of day?"
### Morning Checklist
- [ ] Daily note created
- [ ] Yesterday's incomplete tasks reviewed
- [ ] ONE priority identified
- [ ] Time blocks set
- [ ] Potential obstacles identified
## Midday Check-in (2-3 minutes)
### Quick Review
1. Check morning task completion
2. Compare actual vs planned time use
3. Assess energy level
4. Identify afternoon priorities
### Adjustments
- Reschedule incomplete morning tasks
- Add urgent items that emerged
- Reorder by current energy level
- Note any blockers
### Midday Questions
- "How's your energy right now?"
- "What's the most important thing for this afternoon?"
- "What can you let go of today?"
## Evening Shutdown (5 minutes)
### Capture
1. Mark completed tasks with [x]
2. Add notes and learnings
3. Log energy levels (1-10)
4. Record gratitude items
### Reflect
- What went well today?
- What could be better?
- What did I learn?
- What am I grateful for?
### Prepare
1. Identify tomorrow's priority (preview)
2. Move incomplete tasks to tomorrow or delete
3. Commit changes to git (`/push`)
### Shutdown Checklist
- [ ] All tasks updated (done/moved/deleted)
- [ ] Reflection completed
- [ ] Tomorrow's priority identified
- [ ] Changes committed
## Daily Note Sections
Standard daily note structure:
```markdown
# {{date}}
## Focus
> What's the ONE thing that would make today successful?
## Time Blocks
- 🌅 Morning (9-12):
- ☀️ Afternoon (12-5):
- 🌙 Evening (5+):
## Tasks
### Must Do Today
- [ ]
### Work
- [ ]
### Personal
- [ ]
## Notes
[Capture thoughts, meeting notes, ideas]
## Reflection
- **Wins:**
- **Challenges:**
- **Learned:**
- **Grateful for:**
- **Energy:** /10
- **Tomorrow's priority:**
```
## Time Block Strategies
### Energy-Based
- High energy tasks in morning
- Administrative work after lunch
- Creative work when naturally alert
### Context-Based
- Batch similar tasks together
- Minimize context switching
- Protect deep work blocks
## Integration
Works with:
- `/daily` command for note creation
- `/push` command for end-of-day commit
- Productivity Coach for accountability
- Goal Tracking skill for alignment

View File

@@ -0,0 +1,127 @@
---
name: goal-tracking
description: Track progress toward 3-year, yearly, monthly, and weekly goals. Calculate completion percentages, surface stalled goals, connect daily tasks to objectives. Use for goal reviews and progress tracking.
allowed-tools: Read, Grep, Glob, Edit
---
# Goal Tracking Skill
Track and manage the cascading goal system from long-term vision to daily tasks.
## Goal Hierarchy
```
Goals/0. Three Year Goals.md <- Vision (Life areas)
Goals/1. Yearly Goals.md <- Annual objectives
Goals/2. Monthly Goals.md <- Current month focus
Goals/3. Weekly Review.md <- Weekly planning
Daily Notes/*.md <- Daily tasks and actions
```
## Goal File Formats
### Three Year Goals
```markdown
## Life Areas
- Career: [Vision statement]
- Health: [Vision statement]
- Relationships: [Vision statement]
- Financial: [Vision statement]
- Learning: [Vision statement]
- Personal: [Vision statement]
```
### Yearly Goals
```markdown
## 2024 Goals
- [ ] Goal 1 (XX% complete)
- [ ] Goal 2 (XX% complete)
- [x] Goal 3 (100% complete)
```
### Monthly Goals
```markdown
## This Month's Focus
1. **Primary:** [Main focus]
2. **Secondary:** [Supporting goal]
3. **Stretch:** [If time permits]
### Key Results
- [ ] Measurable outcome 1
- [ ] Measurable outcome 2
```
## Progress Calculation
### Checklist-Based Goals
```
Progress = (Completed checkboxes / Total checkboxes) * 100
```
### Metric-Based Goals
```
Progress = (Current value / Target value) * 100
```
### Time-Based Goals
```
Progress = (Days elapsed / Total days) * 100
```
## Common Operations
### View Goal Progress
1. Read all goal files
2. Parse checkbox completion rates
3. Calculate overall and per-goal progress
4. Identify stalled or at-risk goals
### Update Goal Status
1. Find goal in appropriate file
2. Update checkbox or percentage
3. Add date stamp for significant milestones
4. Update related weekly review
### Connect Task to Goal
When adding tasks to daily notes:
1. Identify which goal the task supports
2. Add goal reference: `Supports: [[1. Yearly Goals#Goal Name]]`
3. Use appropriate priority tag
### Surface Stalled Goals
1. Check last activity date for each goal
2. Flag goals with no progress in 14+ days
3. Suggest actions to restart momentum
## Progress Report Format
```markdown
## Goal Progress Report
### Overall: XX%
### By Goal
| Goal | Progress | Last Activity | Status |
|------|----------|---------------|--------|
| Goal 1 | 75% | 2 days ago | On Track |
| Goal 2 | 30% | 14 days ago | Stalled |
### This Week's Contributions
- [Task] -> [[Goal 1]]
- [Task] -> [[Goal 2]]
### Recommended Focus
1. [Stalled goal needs attention]
2. [Nearly complete goal - finish it]
```
## Integration Points
- Weekly review: Full progress assessment
- Daily planning: Surface relevant goals
- Monthly review: Adjust goals as needed
- Quarterly review: Cascade from 3-year vision

View File

@@ -0,0 +1,95 @@
---
name: obsidian-vault-ops
description: Read and write Obsidian vault files, manage wiki-links, process markdown with YAML frontmatter. Use when working with vault file operations, creating notes, or managing links.
allowed-tools: Read, Write, Edit, Glob, Grep
---
# Obsidian Vault Operations Skill
Core operations for reading, writing, and managing files in an Obsidian vault.
## Vault Structure
```
vault-root/
├── CLAUDE.md # Main context (always read first)
├── Daily Notes/ # YYYY-MM-DD.md format
├── Goals/ # Goal cascade files
├── Projects/ # Project folders with CLAUDE.md
├── Templates/ # Reusable note structures
└── Archives/ # Completed/inactive content
```
## File Operations
### Reading Notes
- Use Glob to find files: `*.md`, `Daily Notes/*.md`
- Read CLAUDE.md first for vault context
- Check for wiki-links to related notes
### Creating Notes
1. Check if note already exists
2. Use appropriate template if available
3. Add YAML frontmatter with date and tags
4. Insert wiki-links to related notes
### Editing Notes
- Preserve YAML frontmatter structure
- Maintain existing wiki-links
- Use consistent heading hierarchy
- Apply standard tag format
## Wiki-Link Format
```markdown
[[Note Name]] # Simple link
[[Note Name|Display Text]] # Link with alias
[[Note Name#Section]] # Link to section
```
## YAML Frontmatter
Standard frontmatter structure:
```yaml
---
date: 2024-01-15
tags: [tag1, tag2]
status: active
---
```
## Template Variables
When processing templates, replace:
- `{{date}}` - Today's date (YYYY-MM-DD)
- `{{date:format}}` - Formatted date
- `{{date-1}}` - Yesterday
- `{{date+1}}` - Tomorrow
- `{{time}}` - Current time
## Common Patterns
### Daily Note Creation
1. Calculate today's date in YYYY-MM-DD format
2. Check if `Daily Notes/{date}.md` exists
3. If not, read `Templates/Daily Template.md`
4. Replace template variables
5. Write to `Daily Notes/{date}.md`
### Finding Related Notes
1. Extract key terms from current note
2. Search vault for matching content
3. Suggest wiki-links to related notes
### Tag Operations
- Priority: `#priority/high`, `#priority/medium`, `#priority/low`
- Status: `#active`, `#waiting`, `#completed`, `#archived`
- Context: `#work`, `#personal`, `#health`, `#learning`
## Best Practices
1. Always check CLAUDE.md for vault-specific conventions
2. Preserve existing structure when editing
3. Use relative paths for internal links
4. Add frontmatter to new notes
5. Link to relevant goals when creating tasks