brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
weeklyFacilitate weekly review process with reflection, goal alignment, and planning. Create review notes, analyze past week, plan next week. Use on Sundays or whenever doing weekly planning.
Independent GitHub snapshot · Automated classification · Original documentation governs
Facilitates your weekly review process by creating a review note and guiding reflection on the past week while planning the next.
Invoke with /weekly or ask Claude to help with your weekly review.
/weekly
Creates Weekly Review Note
Guides Review Process
Automates Housekeeping
Projects/*/CLAUDE.md for current statusThe skill guides you through:
"What were your top 3 wins this week?"
"What were your main challenges?"
"What's your ONE big thing next week?"
# Weekly Review: YYYY-MM-DD
## Last Week's Wins
1.
2.
3.
## Challenges & Lessons
- Challenge:
- Lesson:
## Goal Progress
### Monthly Goals
- [ ] Goal 1 (XX%)
- [ ] Goal 2 (XX%)
### This Week's Contribution
- [Task] -> [[Goal]]
## Project Progress
| Project | Phase | Progress | Next Action |
|---------|-------|----------|-------------|
| [[ProjectA]] | Active | 60% | [Next step] |
| [[ProjectB]] | Planning | 10% | [Next step] |
## Next Week Planning
### ONE Big Thing
>
### Key Tasks
- [ ]
- [ ]
- [ ]
### Project Next-Actions
- [ ] [ProjectA] - [specific next step]
- [ ] [ProjectB] - [specific next step]
### Time Blocks
- Monday:
- Tuesday:
- Wednesday:
- Thursday:
- Friday:
## Notes
Suggest moving daily notes older than 30 days to Archives.
For each active project:
Calculate habit success rates from daily notes:
The weekly skill uses session tasks to show progress through the 3-phase review.
Create tasks at skill start:
TaskCreate:
subject: "Phase 1: Collect"
description: "Gather daily notes from past week, extract wins and challenges"
activeForm: "Collecting daily notes and extracting highlights..."
TaskCreate:
subject: "Phase 2: Reflect"
description: "Calculate goal progress, analyze alignment gaps"
activeForm: "Calculating goal progress and alignment..."
TaskCreate:
subject: "Phase 3: Plan"
description: "Identify ONE Big Thing, plan daily focus areas for next week"
activeForm: "Planning next week's focus..."
Phases must run in order:
TaskUpdate: "Phase 2: Reflect", addBlockedBy: [phase-1-collect-id]
TaskUpdate: "Phase 3: Plan", addBlockedBy: [phase-2-reflect-id]
Reflect is blocked until Collect completes. Plan is blocked until Reflect completes. This provides visibility into the 30-minute review process.
Mark each task in_progress when starting, completed when done using TaskUpdate.
Task tools are session-scoped and don't persist between Claude sessions—your actual weekly review content is saved in the review note.
For a faster, more thorough weekly review, use agent teams to parallelize the collection phase:
Team Lead (coordinator)
├── collector agent — Read all daily notes, extract wins/challenges/tasks
├── goal-analyzer agent — Read goal files, calculate progress, find gaps
└── project-scanner agent — Scan Projects/*/CLAUDE.md, get status updates
When invoking /weekly, you can request the team-based approach:
/weekly
"Use the team approach for a thorough review"
The team lead:
This makes the review faster (parallel collection) and more thorough (dedicated analysis per area).
The weekly review can optionally include a vault health check using multiple agents:
Request with: "Include a vault health check in my weekly review"
Works with:
/daily - Reviews daily notes from the week/monthly - Weekly reviews feed monthly rollup/project - Project status in review/push - Commit after completing review/onboard - Load context for informed review