Noah Brier
f609668172
Claude Code + Obsidian starter kit for AI-powered knowledge management. Features: - PARA method folder structure - Bootstrap initialization system - Pre-configured Claude Code commands and agents - Gemini Vision MCP server with video support - Helper scripts for vault management - Automated release management See README.md for setup instructions.
105 lines
2.6 KiB
Markdown
105 lines
2.6 KiB
Markdown
# 🎯 Projects
|
|
|
|
Active initiatives with specific outcomes and deadlines.
|
|
|
|
## Purpose
|
|
|
|
Projects are **time-bound efforts** with:
|
|
- Clear objectives and deliverables
|
|
- Defined start and end dates
|
|
- Specific success criteria
|
|
- Measurable outcomes
|
|
|
|
## What Belongs Here
|
|
|
|
### Good Projects
|
|
- "Q1 2024 Marketing Strategy" ✓
|
|
- "Website Redesign" ✓
|
|
- "Book Writing - AI & Creativity" ✓
|
|
- "Conference Talk - BRXND NYC" ✓
|
|
|
|
### Not Projects (These go in Areas)
|
|
- "Health" ✗ (ongoing, no end date)
|
|
- "Learning" ✗ (continuous activity)
|
|
- "Team Management" ✗ (ongoing responsibility)
|
|
|
|
## Project Structure
|
|
|
|
Each project should have:
|
|
```
|
|
Project_Name/
|
|
├── README.md # Project overview and status
|
|
├── Research/ # Background materials
|
|
├── Daily_Progress/ # Log of work sessions
|
|
├── Drafts/ # Work in progress
|
|
├── Resources/ # Supporting documents
|
|
└── Output/ # Final deliverables
|
|
```
|
|
|
|
## Claude Code Workflows
|
|
|
|
### Starting a Project
|
|
```
|
|
Create a new project called [name] in 01_Projects.
|
|
Set it up with the standard folder structure.
|
|
I'm in thinking mode - help me define objectives.
|
|
```
|
|
|
|
### Project Research
|
|
```
|
|
I'm working on [project name].
|
|
Search my vault for relevant existing notes.
|
|
What connections exist to my other work?
|
|
```
|
|
|
|
### Daily Progress
|
|
```
|
|
Create a progress note for today in [project]/Daily_Progress.
|
|
Here's what I accomplished: [summary]
|
|
Questions that came up: [list]
|
|
```
|
|
|
|
### Project Status
|
|
```
|
|
Review all notes in [project folder].
|
|
What's the current status?
|
|
What are the key insights so far?
|
|
What's left to complete?
|
|
```
|
|
|
|
### Project Completion
|
|
```
|
|
Project [name] is complete.
|
|
Create a retrospective covering:
|
|
- Objectives vs outcomes
|
|
- Key learnings
|
|
- What to do differently next time
|
|
Then help me archive it properly.
|
|
```
|
|
|
|
## Project Lifecycle
|
|
|
|
1. **Initiation**: Define objectives, success criteria
|
|
2. **Research**: Gather relevant information
|
|
3. **Development**: Daily progress, iterative work
|
|
4. **Review**: Regular status checks
|
|
5. **Completion**: Final output, retrospective
|
|
6. **Archive**: Move to 04_Archive with summary
|
|
|
|
## Tips for Success
|
|
|
|
- **Start with clear objectives** - Vague projects never end
|
|
- **Use the template** - Consistency helps Claude Code help you
|
|
- **Log progress daily** - Even "no progress" is worth noting
|
|
- **Review weekly** - Keep projects on track
|
|
- **Complete or kill** - Don't let projects linger
|
|
|
|
## When to Archive
|
|
|
|
Move projects to `04_Archive/` when:
|
|
- All objectives are complete
|
|
- The project is cancelled
|
|
- It's been inactive for 30+ days
|
|
- It's transformed into an Area (ongoing)
|
|
|
|
Always create a summary note before archiving! |