Installs into .claude/skills of the current project.
Are you the author of Weekly Review?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/kbanc85-weekly-review)
---
name: weekly-review
description: Guided weekly reflection across all relationships, commitments, and projects. Use at end of week or when user says "let's do a weekly review".
effort-level: high
---
# Weekly Review
Guided weekly reflection across all relationships, commitments, and projects.
## The Flow
### 1. Opening Check-In
Start with energy and reflection:
- "How are you feeling about this week?"
- "What's on your mind going into this review?"
### 2. Wins Capture
Surface and celebrate:
- "What went well this week?"
- Check for completed commitments
- Note any positive signals from relationships
- Acknowledge progress
### 3. Commitment Audit
Review all commitments:
**Overdue:**
- What slipped and why?
- Recovery plan or decision to drop?
**Completed:**
- Mark as done
- Any follow-up needed?
**Coming Up:**
- Next week's deadlines
- Anything to start now?
### 4. Waiting Items Review
Check `context/waiting.md`:
- What arrived?
- What's overdue?
- Follow-ups needed?
### 5. Relationship Health
Scan all people files:
- Who needs attention?
- Any cooling relationships?
- Positive momentum to maintain?
### 6. Pattern Reflection
Surface observations from `context/patterns.md`:
- What's working?
- What keeps recurring that shouldn't?
- Any insights for next week?
### 7. Development Check
Reflect on growth (reference `context/me.md` if future direction exists):
- "What worked particularly well this week? Worth remembering or sharing?"
- "Any insights that could become content or methodology improvements?"
- "Progress toward your bigger goals?"
If they shared a future direction during onboarding, connect this week's work to that trajectory. Not every week needs to be about big goals, but it's worth asking.
### 8. Next Week Setup
Look ahead:
- Key priorities
- Important meetings
- Things to start
### 9. Learnings Capture
Before closing:
- Anything to remember for next time?
- Updates to context files?
- Insights worth capturing in `context/me.md`?
## Output Format
```
**π Weekly Review β [Week of Date]**
### π Wins
- [Win 1]
- [Win 2]
- [Win 3]
### π Commitments
**β Completed:**
- [Item] β
**β οΈ Overdue:**
- [Item] β [decision: reschedule/drop/do now]
**π Next Week:**
- [Item] β due [day]
### β³ Waiting On
**Received:**
- [Item] from [Person] β
**Still Waiting:**
- [Item] from [Person] β follow up [when]
### π₯ Relationships
**Need Attention:**
- [Person] β [why]
**Going Well:**
- [Person] β [positive note]
### π Patterns Noticed
- [Pattern or observation]
### π± Development
**What worked well:**
- [Insight worth remembering or sharing]
**Progress toward goals:**
- [Connection to bigger picture, if applicable]
**Ideas captured:**
- [Content ideas, methodology improvements, lessons learned]
### π― Next Week's Focus
1. [Priority 1]
2. [Priority 2]
3. [Priority 3]
### π Notes
- [Anything to remember]
---
```
## Tone
- Reflective, not judgmental
- Celebrate wins genuinely
- Be honest about what slipped without making it feel like failure
- Forward-looking and energizing
- Suggest, don't prescribe
## Timing
Ideal for Friday afternoon or Sunday evening. Adapt based on user preference.
## Depth
The review can be quick (15 min) or thorough (45 min) depending on the week and user's energy. Ask:
"Full review or quick check-in today?"