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>
3.0 KiB
3.0 KiB
paths
| paths |
|---|
| Projects/**/*.md |
Project Management Rules
These conventions apply to project folders and documentation.
Project Structure
Each project gets its own folder:
Projects/
└── Project-Name/
├── CLAUDE.md # Required: Project context for AI
├── README.md # Optional: Overview if complex
├── notes/ # Optional: Related notes
└── resources/ # Optional: Reference materials
Project CLAUDE.md
Every project must have a CLAUDE.md file with:
# Project: [Name]
## Overview
[1-2 sentence description of what this project is]
## Status
- **Phase:** Planning | Active | On Hold | Complete
- **Progress:** X%
- **Started:** YYYY-MM-DD
- **Target:** YYYY-MM-DD
## Goals
What success looks like for this project.
## Current Focus
What I'm actively working on right now.
## Key Decisions
Important decisions made and their rationale.
## Next Actions
- [ ] Immediate next step
- [ ] Following step
## Blockers
Anything preventing progress.
## Resources
- [[Related Note]]
- [External Link](url)
## Notes for Claude
[Any specific context Claude should know when helping with this project]
Project Status Values
Use consistent status labels:
Planning- Defining scope and approachActive- Currently being worked onOn Hold- Temporarily paused (note reason)Blocked- Waiting on external dependencyReview- Work complete, needs reviewComplete- Done and ready for archive
Progress Tracking
Percentage Guidelines
- 0-10%: Planning and setup
- 10-30%: Initial implementation
- 30-70%: Core work
- 70-90%: Refinement and polish
- 90-100%: Final review and completion
Update Frequency
- Update progress weekly at minimum
- Update status when it changes
- Update blockers immediately
Linking Projects
To Goals
Link projects to their parent goals:
**Supports:** [[1. Yearly Goals#Goal Name]]
To Daily Notes
Reference project work in daily notes:
## Work Log
- Worked on [[Project Name]] - completed X
Between Projects
Link related projects:
**Related:** [[Other Project]]
Project Lifecycle
Starting a Project
- Create folder in
Projects/ - Create CLAUDE.md from template
- Link to relevant goal
- Define first next action
- Set target completion date
During Project
- Update CLAUDE.md with progress
- Log work in daily notes
- Capture decisions and rationale
- Track blockers immediately
- Adjust timeline if needed
Completing a Project
- Update status to Complete
- Add completion date and summary
- Document lessons learned
- Move folder to Archives/Projects/
- Update goal progress
Best Practices
- Keep project scope realistic
- One primary focus at a time
- Break large projects into phases
- Review all active projects weekly
- Archive completed projects promptly
- Document decisions as they're made
- Link to relevant context liberally