weekly

Name: weekly
Author: kv0906

134stars33forks

How to install weekly?

kv0906/pm-kit/weekly

$npx -y skills add kv0906/pm-kit --skill weekly

Installs into the current project.

Summary

Weekly review — 3-phase process (Collect/Reflect/Plan). Reviews shipped items, blockers, decisions, and plans next week. Use on Fridays or Mondays.

Files · 1

View on GitHub

SKILL.md

1	# /weekly — Weekly Review
2
3	Facilitates your weekly review by collecting the past week's data, reflecting on progress, and planning the next week.
4
5	## Context
6
7	Today's date: `!date +%Y-%m-%d`
8
9	Config: @_core/config.yaml
10	Processing logic: @_core/PROCESSING.md
11
12	Reference template: @_templates/sprint-retro.md
13
14	## Session Task Progress
15
16	Create tasks at skill start with dependencies:
17
18	```
19	TaskCreate: "Phase 1: Collect"
20	description: "Gather daily notes, shipped items, blockers from past week"
21	activeForm: "Collecting weekly data..."
22
23	TaskCreate: "Phase 2: Reflect"
24	description: "Analyze patterns, what worked/didn't"
25	activeForm: "Reflecting on weekly performance..."
26
27	TaskCreate: "Phase 3: Plan"
28	description: "Set next week priorities, identify top risks"
29	activeForm: "Planning next week..."
30	```
31
32	Set dependencies:
33	```
34	TaskUpdate: "Phase 2", addBlockedBy: [phase-1-id]
35	TaskUpdate: "Phase 3", addBlockedBy: [phase-2-id]
36	```
37
38	## Phase 1: Collect (10 minutes)
39
40	1. Read all daily notes from the past 7 days
41	2. For each active project, aggregate:
42	- Shipped items
43	- Items carried over (WIP)
44	- Blockers resolved
45	- Blockers still open
46	3. Read recent decisions
47	4. Identify patterns in standup data
48
49	## Phase 2: Reflect (10 minutes)
50
51	1. Identify what went well / didn't go well
52	2. Surface recurring patterns (e.g., same blocker type)
53	3. Check: which shipped items had the most impact?
54	4. Check: which blockers slowed progress most?
55	5. Note any decisions that need revisiting
56
57	## Phase 3: Plan (10 minutes)
58
59	1. Set top 3 priorities for next week with owner + due
60	2. Identify decisions that need to be made
61	3. Anticipate blockers (risk watchlist)
62	4. Note any carry-over items
63
64	## Output
65
66	Create weekly review note using template:
67	- Filename: `reports/{date}-sprint-retro.md`
68
69	## Export (Optional)
70
71	Supports `--xlsx`, `--pdf`, `--pptx` flags. See `.claude/rules/export-formats.md` for layout specs and workflow. Complete normal processing first, then generate the formatted file.
72
73	## Integration
74
75	Works with:
76	- `/daily` - Reviews daily notes from the week
77	- `/push` - Commit after completing review
78	- `/onboard` - Load context for informed review
79	- `/progress` - Detailed project status during review

People who liked this also viewed

6 picks

Type

weekly

134stars33forks

View on GitHub

How to install weekly?

kv0906/pm-kit/weekly

$npx -y skills add kv0906/pm-kit --skill weekly

Installs into the current project.

Summary

Weekly review — 3-phase process (Collect/Reflect/Plan). Reviews shipped items, blockers, decisions, and plans next week. Use on Fridays or Mondays.

Files · 1

View on GitHub

SKILL.md

1	# /weekly — Weekly Review
2
3	Facilitates your weekly review by collecting the past week's data, reflecting on progress, and planning the next week.
4
5	## Context
6
7	Today's date: `!date +%Y-%m-%d`
8
9	Config: @_core/config.yaml
10	Processing logic: @_core/PROCESSING.md
11
12	Reference template: @_templates/sprint-retro.md
13
14	## Session Task Progress
15
16	Create tasks at skill start with dependencies:
17
18	```
19	TaskCreate: "Phase 1: Collect"
20	description: "Gather daily notes, shipped items, blockers from past week"
21	activeForm: "Collecting weekly data..."
22
23	TaskCreate: "Phase 2: Reflect"
24	description: "Analyze patterns, what worked/didn't"
25	activeForm: "Reflecting on weekly performance..."
26
27	TaskCreate: "Phase 3: Plan"
28	description: "Set next week priorities, identify top risks"
29	activeForm: "Planning next week..."
30	```
31
32	Set dependencies:
33	```
34	TaskUpdate: "Phase 2", addBlockedBy: [phase-1-id]
35	TaskUpdate: "Phase 3", addBlockedBy: [phase-2-id]
36	```
37
38	## Phase 1: Collect (10 minutes)
39
40	1. Read all daily notes from the past 7 days
41	2. For each active project, aggregate:
42	- Shipped items
43	- Items carried over (WIP)
44	- Blockers resolved
45	- Blockers still open
46	3. Read recent decisions
47	4. Identify patterns in standup data
48
49	## Phase 2: Reflect (10 minutes)
50
51	1. Identify what went well / didn't go well
52	2. Surface recurring patterns (e.g., same blocker type)
53	3. Check: which shipped items had the most impact?
54	4. Check: which blockers slowed progress most?
55	5. Note any decisions that need revisiting
56
57	## Phase 3: Plan (10 minutes)
58
59	1. Set top 3 priorities for next week with owner + due
60	2. Identify decisions that need to be made
61	3. Anticipate blockers (risk watchlist)
62	4. Note any carry-over items
63
64	## Output
65
66	Create weekly review note using template:
67	- Filename: `reports/{date}-sprint-retro.md`
68
69	## Export (Optional)
70
71	Supports `--xlsx`, `--pdf`, `--pptx` flags. See `.claude/rules/export-formats.md` for layout specs and workflow. Complete normal processing first, then generate the formatted file.
72
73	## Integration
74
75	Works with:
76	- `/daily` - Reviews daily notes from the week
77	- `/push` - Commit after completing review
78	- `/onboard` - Load context for informed review
79	- `/progress` - Detailed project status during review

People who liked this also viewed

6 picks

Type