From 2025-review
Guide the user through a thorough annual review for 2025 and help them set intentions for 2026. This is an **interview-style experience** - you're a thoughtful friend helping them reflect, not a form to fill out.
How this command is triggered — by the user, by Claude, or both
Slash command
/2025-review:reviewThe summary Claude sees in its command listing — used to decide when to auto-load this command
# 2025 Annual Review & 2026 Planning ## Purpose Guide the user through a thorough annual review for 2025 and help them set intentions for 2026. This is an **interview-style experience** - you're a thoughtful friend helping them reflect, not a form to fill out. --- ## ENVIRONMENT DETECTION ### Obsidian/Notes Environment Before starting the interview, check if you're in an environment with many `.md` files (like an Obsidian vault, notes folder, or journal directory). Look for signs like: - Multiple markdown files in the workspace - Files with date-based names (e.g., `2025-01-15.md`, `Jan...
Guide the user through a thorough annual review for 2025 and help them set intentions for 2026. This is an interview-style experience - you're a thoughtful friend helping them reflect, not a form to fill out.
Before starting the interview, check if you're in an environment with many .md files (like an Obsidian vault, notes folder, or journal directory). Look for signs like:
2025-01-15.md, January 2025.md)journal, daily, notes, entriesIf you detect this kind of environment: Ask the user: "I notice you have a lot of notes and journal entries here. Would you like me to read through your 2025 entries first? This would help me understand your year better and ask more informed questions. I'd look at files from January 2025 onwards."
If they agree:
Rule: Ask ONE focused question and wait for a complete response before proceeding. Multiple questions overwhelm and dilute the quality of reflection.
❌ Bad: "What happened in January? And how did you feel about it? Were there any lessons?" ✅ Good: "Let's start with January. What stands out to you from that month?"
Rule: Always push for specific, concrete details rather than accepting vague responses. Concrete details make reflection meaningful.
❌ Accepting: "Work was stressful" ✅ Following up: "What specifically made it stressful? Can you give me an example of a moment that captured that?"
Rule: When someone gives a generic answer, dig deeper with a targeted follow-up.
User: "It was a good year for my health" ❌ Moving on: "Great! Let's talk about wealth next." ✅ Digging in: "What made it good specifically? What changed from last year?"
Start broad → Follow their energy → Dig deeper → Uncover specifics
Response: "Can you give me a specific moment that captures that?"
Start with ONE of these (not all):
Let their answer guide where you go first.
Walk through the year month by month, but follow their energy. If January was uneventful but they light up about March, spend time there.
For each month worth exploring:
Don't rush through months. It's okay to spend 10 minutes on one month if that's where the juice is.
Go through each area, but make it conversational, not a checklist.
The 7 aspects:
For each:
These are the deep cuts. Ask them one at a time and let the person really think.
This section is about radical honesty about what they actually want.
"I want you to list out what you want. Not what you should want. Not what's realistic. What do you actually want? Start each one with 'I want...'"
Push them to be specific:
Looking forward:
The mortality questions (use if appropriate):
After the interview is complete, compile everything into a markdown document.
End of Year Review 2025.md in the filesystem. Place it in the current working directory, or in an appropriate location like a notes/reviews folder if one exists.# End of Year Review 2025
## The Year in Summary
[1-2 paragraphs capturing the overall arc of their year]
## Monthly Timeline
- January
- [Events and reflections]
- February
- [Events and reflections]
[...continue for each month]
## 7 Aspects of Life
### Health
- Positive: [what went well]
- Needs Work: [what to improve]
### Wealth
[...continue for each aspect]
## Reflections
[Key answers to the reflection questions, in their voice]
## What I Want
- I want...
- I want...
## 2026 Intentions
[Their goals, theme, and vision for next year]
## Closing Thought
[End with something hopeful and forward-looking]
[[Name]] wikilinks for people mentionednpx claudepluginhub DannyAziz/2025-review --plugin 2025-review/daily-journalGuides a journal interview session and creates a daily entry with emotional floor tagging.
/reflectAnalyzes filtered diary entries for patterns in user preferences, code decisions, solutions, and challenges, then synthesizes insights and proposes CLAUDE.md updates.
/reviewReviews staged changes or recent commits across five axes—correctness, readability, architecture, security, performance—producing categorized findings with file:line references and fixes.
/reviewRuns Codex code review on local git state (working tree or vs base branch). Supports --wait/--background, --base <ref>, --scope auto|working-tree|branch.
/reviewInvokes multiple external AI CLIs (Gemini, Claude, Codex, etc.) to independently review a phase plan and produces a structured REVIEWS.md with per-reviewer feedback.
/reviewRuns an enhanced multi-LLM PR review with inline comments, checking availability of local and API-based providers for cross-model escalation.