Files
my-vault/WEEKLY_REVIEW.md
T
windyboy 8e3943f064 Initial vault setup with PARA structure
- Created CLAUDE.md configuration file
- Created WEEKLY_REVIEW.md template
- Set up PARA folder structure (Projects, Areas, Resources, Archive)
- Created README files for each main folder
- Configured .gitignore for vault files
- Saved vault configuration to .claude/vault-config.json

Generated with Claude Code
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-01-05 21:10:11 +08:00

11 KiB

Weekly Review Template

Review Date: [YYYY-MM-DD] Week Number: [Week N of 2026] Reviewer: [Your Name or "Self Review"]


Pre-Review Checklist

  • git pull - Sync latest changes from remote
  • git status - Check for uncommitted changes
  • Commit any pending work before starting review
  • Block 30-45 minutes of uninterrupted time
  • Have pen and paper ready for notes

1. Inbox Processing

Goal: Zero inbox (except permanent files)

Step 1: Count Current Inbox Items

ls 00_Inbox/ | wc -l

Current Count: _____ items (excluding permanent files)

Step 2: Quick Delete

Review and delete:

  • Obsolete information
  • Duplicate notes
  • Low-value clippings
  • Test files
  • Outdated drafts

Deleted: _____ items

Step 3: Process Remaining Items

For each item in inbox, decide:

Filename Action Destination Status
Delete / Move / Process [ ]
Delete / Move / Process [ ]
Delete / Move / Process [ ]
Delete / Move / Process [ ]
Delete / Move / Process [ ]

Step 4: Process Clippings Folder

ls 00_Inbox/Clippings/
  • Review all web clippings from Firecrawl
  • Add context and notes to valuable clippings
  • Move to appropriate PARA locations
  • Delete low-value or duplicate content

Clippings processed: _____ items

Step 5: Verify Empty Inbox

ls 00_Inbox/

Final Count: _____ items (should be just permanent files)

  • Inbox is clean and organized

2. Projects Review

Step 1: List All Active Projects

ls 01_Projects/

Active Projects Count: _____

Step 2: Review Each Project

For each project in 01_Projects/:

Project: _____________________

  • Status: [ ] On Track [ ] Behind [ ] Blocked [ ] Complete
  • Progress this week: ________________________________
  • Next action: ________________________________________
  • Blockers: ___________________________________________
  • Needs:
    • More research
    • External input
    • Time allocation
    • Resources/tools
    • Other: __________

Project: _____________________

  • Status: [ ] On Track [ ] Behind [ ] Blocked [ ] Complete
  • Progress this week: ________________________________
  • Next action: ________________________________________
  • Blockers: ___________________________________________
  • Needs:
    • More research
    • External input
    • Time allocation
    • Resources/tools
    • Other: __________

Project: _____________________

  • Status: [ ] On Track [ ] Behind [ ] Blocked [ ] Complete
  • Progress this week: ________________________________
  • Next action: ________________________________________
  • Blockers: ___________________________________________
  • Needs:
    • More research
    • External input
    • Time allocation
    • Resources/tools
    • Other: __________

Step 3: Identify Completed Projects

Projects to archive:

  • Project: ______________ (completed ______)
  • Project: ______________ (completed ______)
  • Project: ______________ (completed ______)

Archive Process:

mv "01_Projects/[ProjectName]" "04_Archive/Projects/[ProjectName]"
  • All completed projects moved to Archive
  • Project completion notes created
  • Related area notes updated

Step 4: Identify Stalled Projects

Projects inactive for 30+ days:

  • Project: ______________
    • Reactivate
    • Archive
    • Convert to Area/Resource

Action taken: _________________________________

Step 5: New Projects Needed

Emerging projects from areas or inbox:

  • New project: _____________________ (from Area: ______)
  • New project: _____________________ (from Area: ______)
  • New project: _____________________ (from Inbox item)

Created:

mkdir -p "01_Projects/[ProjectName]/{Research,Drafts,Output}"
  • New project folders created
  • README.md added with objectives
  • Initial files moved to project

3. Areas Review

Step 1: List All Areas

ls 02_Areas/

Areas Count: _____

Step 2: Review Each Area

For each area in 02_Areas/:

Area: _____________________

  • Health: [ ] Excellent [ ] Good [ ] Needs Attention [ ] Critical
  • Activity this week: ________________________________
  • Standards met: [ ] Yes [ ] Mostly [ ] No
  • Related projects: ________________________________
  • Action needed:
    • Create new project
    • Update area note
    • Research new approach
    • Archive area
    • Other: __________

Area: _____________________

  • Health: [ ] Excellent [ ] Good [ ] Needs Attention [ ] Critical
  • Activity this week: ________________________________
  • Standards met: [ ] Yes [ ] Mostly [ ] No
  • Related projects: ________________________________
  • Action needed:
    • Create new project
    • Update area note
    • Research new approach
    • Archive area
    • Other: __________

Area: _____________________

  • Health: [ ] Excellent [ ] Good [ ] Needs Attention [ ] Critical
  • Activity this week: ________________________________
  • Standards met: [ ] Yes [ ] Mostly [ ] No
  • Related projects: ________________________________
  • Action needed:
    • Create new project
    • Update area note
    • Research new approach
    • Archive area
    • Other: __________

Step 3: Areas Needing Projects

Areas requiring active projects:

  • Area: ______________ → Project: ______________
  • Area: ______________ → Project: ______________

Step 4: Update Area Notes

  • Review overview notes for each area
  • Update progress and reflections
  • Link to new resources or projects
  • Update frontmatter dates

4. Resources Review

Step 1: List Resources

ls 03_Resources/

Resource Topics Count: _____

Step 2: Quality Check

Recent additions this week:

  • Resource: ______________ (Quality: Good / Medium / Poor)
  • Resource: ______________ (Quality: Good / Medium / Poor)
  • Resource: ______________ (Quality: Good / Medium / Poor)

Step 3: Consolidation Opportunities

Overlapping or duplicate resources:

  • Merge: ______________ + ______________ → ______________
  • Merge: ______________ + ______________ → ______________

Step 4: Outdated Resources

Resources to archive or delete:

  • Archive: ______________ (reason: ______)
  • Delete: ______________ (reason: ______)

Action:

mv "03_Resources/[TopicName]" "04_Archive/Resources/[TopicName]"
  • Outdated resources archived

Step 5: New Resource Topics

Emerging topics to track:

  • Create: 03_Resources/________________/
  • Create: 03_Resources/________________/

5. Attachments Processing

Step 1: List Unprocessed Attachments

ls 05_Attachments/

Unprocessed Count: _____

Or use helper:

pnpm attachments:list

Step 2: Process Each Attachment

For each unprocessed file:

Filename Related Note New Name Action Status
Rename/Move/Delete [ ]
Rename/Move/Delete [ ]
Rename/Move/Delete [ ]
Rename/Move/Delete [ ]

Step 3: Rename and Organize

mv "05_Attachments/[file]" "05_Attachments/Organized/[RelatedNote]_[Description].[ext]"
  • All attachments renamed with clear names
  • Attachments moved to Organized folder
  • Links updated in related notes

Step 4: Find Orphaned Attachments

pnpm attachments:orphans

Orphaned Files: _____

  • Review orphaned files
  • Delete unreferenced files
  • Or add references to notes
pnpm attachments:update-links
  • All attachment links verified and updated

Final Organized Count: _____


6. Git Commit

Step 1: Review Changes

git status

Modified Files: _____ New Files: _____ Deleted Files: _____

Step 2: Review Diff

git diff
  • Reviewed all changes
  • No sensitive information in commit
  • Changes are intentional

Step 3: Stage and Commit

git add .
git commit -m "Weekly review: Week N of 2026 - [Brief summary]"

Commit Message:

Weekly review: Week N of 2026

- Processed inbox: X items
- Archived Y projects
- Updated Z areas
- Organized N attachments
- [Other notable changes]
  • Changes committed with descriptive message

Step 4: Push to Remote

git push
  • Changes pushed to remote repository
  • Verified push succeeded

7. Next Week Planning

Focus Areas

Top 3 Priorities:




Project Focus

Active Projects for Next Week:

  • Project: ________________ (Next action: ______________)
  • Project: ________________ (Next action: ______________)
  • Project: ________________ (Next action: ______________)

Time Allocation

Project/Area Time Commitment Specific Actions
hours
hours
hours

Potential Obstacles

Anticipated Challenges:



Mitigation Strategies:



New Initiatives

To Start Next Week:

  • _____________________________________________
  • _____________________________________________

To Research:

  • _____________________________________________
  • _____________________________________________

8. Reflection

What Went Well This Week




What Needs Improvement




System Adjustments

Workflow Changes Needed:

  • _____________________________________________
  • _____________________________________________

Documentation Updates:

  • Update CLAUDE.md with new practices
  • Create new templates
  • Refine folder structure

Metrics

Completion Stats:

  • Inbox items processed: _____
  • Projects advanced: _____
  • Projects completed: _____
  • Notes created: _____
  • Attachments organized: _____
  • Git commits: _____

Health Check:

  • Inbox under control (< 20 items)
  • All active projects have next actions
  • Areas are maintained
  • Git is synced
  • Attachments organized

Review Complete

  • All sections completed
  • Actions identified and scheduled
  • Git committed and pushed
  • Ready for next week

Review Duration: _____ minutes

Next Review Scheduled: [Date] _______________


Notes:





Template Version: 1.0 Last Updated: January 05, 2026