Agent skill
weekly-review
Weekly review and planning session. Use at end of week or weekend to review progress, plan next week, and set priorities. Triggers on "weekly review", "plan my week", "what did I do this week", "Sunday planning".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/weekly-review-taylorhuston-local-life-manager
SKILL.md
Run a weekly review and planning session. Keep it conversational - one section at a time.
Step 0: Get Week Info
date +%Y-%m-%d # Today
date +%Y-W%V # Current ISO week
date -d "last sunday" +%Y-%m-%d # Week start (for lookback)
Step 1: Weekly Note Setup
- Check if this week's note exists:
my-vault/02 Calendar/YYYY-Www.md - If not, create from
09 System/Templates/Weekly Template.md- Replace Templater placeholders with actual dates
- The week note format is
YYYY-[W]ww(e.g.,2026-W03)
Step 2: Journal Completeness Check
Critical: Verify all 7 days have journal entries and content.
# List last 7 days' journal files
for i in {0..6}; do
d=$(date -d "$i days ago" +%Y-%m-%d)
f="my-vault/02 Calendar/$d.md"
if [[ -f "$f" ]]; then
lines=$(wc -l < "$f")
echo "$d: EXISTS ($lines lines)"
else
echo "$d: MISSING"
fi
done
For each existing entry, check if sections are filled in:
- "# What Did I Do?" - should have content
- "# What Did I Work On?" - should have content
- "# What Did I Study?" - optional but note if empty
Report gaps: "These days are missing entries: ..." or "These entries look empty: ..." Offer to fill in: "Want me to check GitHub for commits on those days to help fill them in?"
Step 3: Review the Week
GitHub Activity (all week)
gh search commits --author=TaylorHuston --committer-date=YYYY-MM-DD..YYYY-MM-DD --limit=50
Summarize by project/repo.
Journal Highlights
Read each day's journal and extract:
- Personal: From "What Did I Do?"
- Technical: From "What Did I Work On?"
- Learning: From "What Did I Study?"
Present as a brief week summary, not raw dump.
Learning Progress
- Check
.claude/learning-sessions/learning-plan.jsonif exists - Note topics covered, sessions completed
Project Progress
- Scan
ideas/*/issues/for any WORKLOG.md updates this week - Note completed tasks, status changes
Step 4: Fill In Weekly Note
Update the weekly note (my-vault/02 Calendar/YYYY-Www.md) sections:
- What Went Well: Ask Taylor
- What Didn't Go Well: Ask Taylor
- Key Accomplishments: Summarize from review
- Lessons Learned: Ask Taylor
Step 5: Plan Next Week
Ask Taylor (one at a time):
- "Any interviews or job search priorities this week?"
- "What's the one thing that would make next week a success?"
- "Any personal commitments to work around?"
Fill in "Next Week's Focus" section with their answers.
Step 6: Memory Capture
Review conversation for memory-worthy items:
- Job search updates
- New preferences or workflow changes
- Project decisions
- Personal context changes
Update .claude/memories/about-taylor.md if job status or major context changed.
Conversational Flow
Don't dump everything at once. Flow should be:
- "Let me check your journal entries for this week..." → Report gaps
- "Here's what I found from your week..." → Brief summary
- "What went well this week?" → Capture response
- "What didn't go well?" → Capture response
- "Any lessons learned?" → Capture response
- "Looking ahead - any job search priorities?" → Plan next week
- "What would make next week a success?" → Set focus
- "I've updated your weekly note. Anything else?"
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?