weekly-plan

Name: weekly-plan
Author: aleksander-dytko

31stars4forks

How to install weekly-plan?

aleksander-dytko/ai-pm-workspace/weekly-plan

$npx -y skills add aleksander-dytko/ai-pm-workspace --skill weekly-plan

Installs into the current project.

Summary

Plan weekly P-Tasks with in-repo task triage and overplanning challenge

Files · 1

View on GitHub

SKILL.md

1	# Plan Weekly P-Tasks
2
3	You help plan the upcoming week's P-Tasks (3-5 meaty priorities) with an overplanning challenge and triage of the in-repo task list.
4
5	## Input
6
7	The user invokes this skill (typically Sunday evening or Monday morning) without arguments, or with context like "plan my week".
8
9	The user may:
10	- Let you suggest P-tasks based on context
11	- Propose their own P-task list for validation
12	- Provide calendar context (screenshot or text)
13
14	## Workflow
15
16	### 1. Review previous week
17
18	Read `Dashboard/Weekly P-Tasks.md`. Find the most recent week's P-tasks.
19
20	If last week's P-tasks don't have completion markers, prompt the user:
21
22	```
23	Let's review last week before planning this week:
24
25	P1: [Task]
26	- Status? (Completed / Partial / Not done)
27	- If completed: results?
28	- If partial or not done: what blocked it?
29
30	P2: [Task]
31	...
32	```
33
34	Wait for review, then update last week's entry with markers:
35	- `✅` completed (add a note about results)
36	- `🔄` partial / carry over (add a note about what's left)
37	- `❌` not started / deprioritized (add a note about why)
38
39	Compute last week's completion rate (completed / total) - used for the overplanning check.
40
41	### 2. Analyze recent daily notes
42
43	Read the last 7 days from `journals/YYYY/MM-Month/`.
44
45	Identify:
46	- Carryover items mentioned but not finished.
47	- Energy/mood patterns from frontmatter and content:
48	- Declining trend (e.g., 7 → 5).
49	- Mentions of overwork, burnout, feeling overwhelmed.
50	- Recurring themes or blockers.
51	- Weekly review notes (Friday entries).
52
53	Capacity adjustment:
54	- Energy < 6 or declining trend → suggest 3-4 P-tasks max.
55	- "Feeling overwhelmed" appears → reduce scope aggressively.
56
57	### 3. Calendar context
58
59	If the user hasn't shared their calendar, ask:
60	"Share your calendar for this week or highlight key deadlines."
61
62	Look for hard deadlines (presentations, demos, deliverables), meeting density, and time-sensitive milestones.
63
64	If calendar shows >50% meeting time: reduce P-task count and note reduced capacity.
65
66	### 4. Review recent meetings for follow-ups
67
68	Read the last 5 meeting notes from `Meetings/`. Extract action items assigned to the user that are still open and not yet in `Dashboard/tasks.md`. Flag them.
69
70	### 5. Read `Dashboard/tasks.md` - triage inputs
71
72	Read `Dashboard/tasks.md`. You now have three buckets:
73
74	- This week - items already committed to this week.
75	- Next - items intended soon but not this week.
76	- Backlog - unscheduled.
77
78	Flag items in "This week" that are stale carryovers (from prior weeks and still open). Flag items in "Backlog" older than 4 weeks that look stale.
79
80	### 5b. Triage - execute immediately
81
82	Goal: Dashboard/tasks.md "This week" contains only what you truly commit to this week.
83
84	Present a triage table:
85
86	```
87	This week leftovers (N tasks)
88	-> "Task A" Keep - still relevant this week
89	-> "Old task X" Move to Next / Backlog - deprioritized
90
91	Backlog promotions (top 5 relevant to this week's themes)
92	-> "Follow up with X" Promote to This week - blocks work
93	-> "Scope workshop Y" Stay in Backlog - not this week
94
95	Stale backlog (4+ weeks old, no notes)
96	-> "Old task" Delete? - no recent activity
97	```
98
99	For each item, suggest an action. Wait for the user to confirm or override, then execute the moves immediately by editing `Dashboard/tasks.md`. Do not wait until the end.
100
101	After triage: confirm "Triage complete - X tasks kept, Y moved, Z deleted."
102
103	### 6. Suggest or validate P-Tasks + standalone tasks
104
105	Two outputs from this step: P-Tasks (with subtasks) and standalone tasks (no subtasks, specific day).
106
107	#### P-Tasks (3-5, each needs subtasks)
108
109	If the user proposed tasks: validate against context (completion rate, calendar, energy). Proceed to step 7.
110
111	If the user wants suggestions: draft 3-5 P-tasks based on:
112	- Carryover from last week
113	- Meeting follow-ups not yet in tasks.md
114	- Triage promotions
115	- Calendar deadlines
116
117	Prioritize P1-P5:
118	- P1 critical, must be done this week (1-2 max)
119	- P2 high priority, significant impact (1-2)
120	- P3 medium priority, should be done (1-2)
121	- P4 low priority, nice to have (0-1)
122	- P5 optional, time permitting (0-1)
123
124	#### Standalone tasks (3-6, self-contained)
125
126	Suggest from:
127	- Triage promotions flagged "this week"
128	- Meeting follow-ups too small for a P-task
129	- Backlog candidates matched to this week's themes
130
131	Assign each standalone task a specific day based on calendar density and P-task load.
132
133	### 7. Validate task quality
134
135	Check each P-task against [quality-checklist.md](quality-checklist.md).
136
137	Good P-task qualities:
138	- Clear, measurable result (not vague)
139	- Specific action verb ("Draft", "Create", "Share")
140	- Noteworthy (not routine)
141	- Requires active effort
142	- Independently achievable
143
144	Red flags:
145	- Vague verbs: "work on", "think about", "look into"
146	- Too small: "send email", "schedule meeting"
147	- Grouped: "create X and Y" (split them)
148	- No clear c

People who liked this also viewed

6 picks

Type

weekly-plan

31stars4forks

View on GitHub

How to install weekly-plan?

aleksander-dytko/ai-pm-workspace/weekly-plan

$npx -y skills add aleksander-dytko/ai-pm-workspace --skill weekly-plan

Installs into the current project.

Summary

Plan weekly P-Tasks with in-repo task triage and overplanning challenge

Files · 1

View on GitHub

SKILL.md

1	# Plan Weekly P-Tasks
2
3	You help plan the upcoming week's P-Tasks (3-5 meaty priorities) with an overplanning challenge and triage of the in-repo task list.
4
5	## Input
6
7	The user invokes this skill (typically Sunday evening or Monday morning) without arguments, or with context like "plan my week".
8
9	The user may:
10	- Let you suggest P-tasks based on context
11	- Propose their own P-task list for validation
12	- Provide calendar context (screenshot or text)
13
14	## Workflow
15
16	### 1. Review previous week
17
18	Read `Dashboard/Weekly P-Tasks.md`. Find the most recent week's P-tasks.
19
20	If last week's P-tasks don't have completion markers, prompt the user:
21
22	```
23	Let's review last week before planning this week:
24
25	P1: [Task]
26	- Status? (Completed / Partial / Not done)
27	- If completed: results?
28	- If partial or not done: what blocked it?
29
30	P2: [Task]
31	...
32	```
33
34	Wait for review, then update last week's entry with markers:
35	- `✅` completed (add a note about results)
36	- `🔄` partial / carry over (add a note about what's left)
37	- `❌` not started / deprioritized (add a note about why)
38
39	Compute last week's completion rate (completed / total) - used for the overplanning check.
40
41	### 2. Analyze recent daily notes
42
43	Read the last 7 days from `journals/YYYY/MM-Month/`.
44
45	Identify:
46	- Carryover items mentioned but not finished.
47	- Energy/mood patterns from frontmatter and content:
48	- Declining trend (e.g., 7 → 5).
49	- Mentions of overwork, burnout, feeling overwhelmed.
50	- Recurring themes or blockers.
51	- Weekly review notes (Friday entries).
52
53	Capacity adjustment:
54	- Energy < 6 or declining trend → suggest 3-4 P-tasks max.
55	- "Feeling overwhelmed" appears → reduce scope aggressively.
56
57	### 3. Calendar context
58
59	If the user hasn't shared their calendar, ask:
60	"Share your calendar for this week or highlight key deadlines."
61
62	Look for hard deadlines (presentations, demos, deliverables), meeting density, and time-sensitive milestones.
63
64	If calendar shows >50% meeting time: reduce P-task count and note reduced capacity.
65
66	### 4. Review recent meetings for follow-ups
67
68	Read the last 5 meeting notes from `Meetings/`. Extract action items assigned to the user that are still open and not yet in `Dashboard/tasks.md`. Flag them.
69
70	### 5. Read `Dashboard/tasks.md` - triage inputs
71
72	Read `Dashboard/tasks.md`. You now have three buckets:
73
74	- This week - items already committed to this week.
75	- Next - items intended soon but not this week.
76	- Backlog - unscheduled.
77
78	Flag items in "This week" that are stale carryovers (from prior weeks and still open). Flag items in "Backlog" older than 4 weeks that look stale.
79
80	### 5b. Triage - execute immediately
81
82	Goal: Dashboard/tasks.md "This week" contains only what you truly commit to this week.
83
84	Present a triage table:
85
86	```
87	This week leftovers (N tasks)
88	-> "Task A" Keep - still relevant this week
89	-> "Old task X" Move to Next / Backlog - deprioritized
90
91	Backlog promotions (top 5 relevant to this week's themes)
92	-> "Follow up with X" Promote to This week - blocks work
93	-> "Scope workshop Y" Stay in Backlog - not this week
94
95	Stale backlog (4+ weeks old, no notes)
96	-> "Old task" Delete? - no recent activity
97	```
98
99	For each item, suggest an action. Wait for the user to confirm or override, then execute the moves immediately by editing `Dashboard/tasks.md`. Do not wait until the end.
100
101	After triage: confirm "Triage complete - X tasks kept, Y moved, Z deleted."
102
103	### 6. Suggest or validate P-Tasks + standalone tasks
104
105	Two outputs from this step: P-Tasks (with subtasks) and standalone tasks (no subtasks, specific day).
106
107	#### P-Tasks (3-5, each needs subtasks)
108
109	If the user proposed tasks: validate against context (completion rate, calendar, energy). Proceed to step 7.
110
111	If the user wants suggestions: draft 3-5 P-tasks based on:
112	- Carryover from last week
113	- Meeting follow-ups not yet in tasks.md
114	- Triage promotions
115	- Calendar deadlines
116
117	Prioritize P1-P5:
118	- P1 critical, must be done this week (1-2 max)
119	- P2 high priority, significant impact (1-2)
120	- P3 medium priority, should be done (1-2)
121	- P4 low priority, nice to have (0-1)
122	- P5 optional, time permitting (0-1)
123
124	#### Standalone tasks (3-6, self-contained)
125
126	Suggest from:
127	- Triage promotions flagged "this week"
128	- Meeting follow-ups too small for a P-task
129	- Backlog candidates matched to this week's themes
130
131	Assign each standalone task a specific day based on calendar density and P-task load.
132
133	### 7. Validate task quality
134
135	Check each P-task against [quality-checklist.md](quality-checklist.md).
136
137	Good P-task qualities:
138	- Clear, measurable result (not vague)
139	- Specific action verb ("Draft", "Create", "Share")
140	- Noteworthy (not routine)
141	- Requires active effort
142	- Independently achievable
143
144	Red flags:
145	- Vague verbs: "work on", "think about", "look into"
146	- Too small: "send email", "schedule meeting"
147	- Grouped: "create X and Y" (split them)
148	- No clear c

People who liked this also viewed

6 picks

Type