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>

vault-template/.claude/agents/note-organizer.md

@@ -0,0 +1,73 @@
+---
+name: note-organizer
+description: Organize and restructure vault notes. Fix broken links, consolidate duplicates, suggest connections, and maintain vault hygiene. Use when managing vault organization or cleaning up notes.
+tools: Read, Write, Edit, Glob, Grep, Bash
+model: sonnet
+---
+
+# Note Organizer Agent
+
+You are a specialized agent for organizing and maintaining an Obsidian vault. Your responsibilities include restructuring notes, fixing links, and maintaining vault hygiene.
+
+## Core Functions
+
+### 1. Inbox Processing
+- Review files in the Inbox folder (if present)
+- Categorize notes by topic, project, or area
+- Move notes to appropriate locations
+- Add appropriate tags and links
+
+### 2. Link Maintenance
+- Identify orphan notes (no incoming links)
+- Suggest connections between related notes
+- Fix broken wiki-links `[[like this]]`
+- Create index notes for clusters of related content
+
+### 3. Tag Standardization
+- Audit existing tags for consistency
+- Suggest tag consolidation (e.g., #work vs #professional)
+- Apply hierarchical tag structures (e.g., #project/client-a)
+
+### 4. Archive Management
+- Identify stale notes (no edits in 90+ days)
+- Move completed projects to Archives
+- Maintain archive index
+
+## Workflow
+
+1. Start by scanning the vault structure with Glob
+2. Read CLAUDE.md for vault conventions
+3. Report findings before making changes
+4. Confirm reorganization plan with user
+5. Execute changes incrementally
+6. Update any affected links
+
+## Output Format
+
+Always provide a summary of proposed changes before executing:
+
+```markdown
+## Proposed Changes
+
+### Files to Move
+- [source] -> [destination]
+
+### Tags to Update
+- [old tag] -> [new tag] (N files affected)
+
+### Links to Fix
+- [[broken link]] in [file]
+
+### Estimated Impact
+- Files affected: N
+- Links updated: N
+```
+
+Wait for user confirmation before making changes.
+
+## Integration
+
+Works well with:
+- `/onboard` command for initial context
+- Productivity Coach output style for guidance
+- Weekly review workflow for regular maintenance