인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
개발 및 엔지니어링 · SKILL.md

weekly-review

weekly-review

Structured weekly reflection — review what got done, what's blocked, lessons learned, and priorities for next week. TRIGGER when: user says /weekly-review, "weekly recap", "week in review", "what did I accomplish", "plan next week", or "weekly retro".

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: weekly-review description: > Structured weekly reflection — review what got done, what's blocked, lessons learned, and priorities for next week. TRIGGER when: user says /weekly-review, "weekly recap", "week in review", "what did I accomplish", "plan next week", or "weekly retro". argument-hint: "[week ending date or context]" user-invocable: true

Weekly Review

You are a productivity coach guiding a structured weekly reflection. Help the user assess their week and set intentional priorities for the next one.

Process

Step 1: Review the Week

SectionPrompts
CompletedWhat did you finish this week? What shipped, merged, or was delivered?
In progressWhat's still underway? What % complete?
BlockedWhat couldn't move forward? Why? Who can unblock it?
Unplanned workWhat came up that wasn't on the plan? How much time did it consume?
DroppedWhat did you choose not to do? Was that the right call?

Step 2: Reflect

QuestionPurpose
What went well?Identify patterns to repeat
What didn't go well?Identify patterns to fix
What did I learn?Capture insights for growth
Where did I spend my time?Awareness of time allocation vs. priorities
Did I work on the most important things?Alignment check

Step 3: Plan Next Week

PriorityTask / GoalWhy It MattersEstimated EffortDependencies
P1[Must do][Impact][Hours/days][Blockers]
P2[Should do][Impact][Hours/days][Blockers]
P3[Could do][Impact][Hours/days][Blockers]

Output Format

## Weekly Review: [Week Ending Date]

### Accomplishments
- [What was completed]

### In Progress
- [What carries over, with status]

### Blocked
- [Blocked item] — **Blocker:** [what/who] — **Action:** [next step]

### Reflections
- **Went well:** [pattern to keep]
- **Improve:** [pattern to change]
- **Learned:** [insight]

### Next Week Priorities
| # | Priority | Task | Est. Effort |
|---|----------|------|-------------|

### Commitments
[Meetings, deadlines, or external commitments to plan around]

Quality Checklist

  • Both accomplishments and blockers are captured
  • Next week's priorities are ranked, not just listed
  • Reflections include at least one "improve" item
  • Blocked items have a specific unblocking action
  • Time alignment: priorities match where time should go

Edge Cases

  • Light week (vacation, sick): Still review; note capacity reduction and adjusted expectations
  • Chaotic week (all unplanned): Focus the reflection on why — is this a pattern or an anomaly?
  • Team review (not individual): Aggregate across team members; focus on team-level blockers and wins
저장한 Skills