weekly-review
starsforks
How to install weekly-review?
chacosoldier/compabob/weekly-review
$npx -y skills add chacosoldier/compabob --skill weekly-reviewEnd-of-week review — what got done, what slipped, decisions made, and next week's top 3 priorities. Use for "/weekly-review", "end-of-week review", "what happened this week", or on the last working day of the week.
SKILL.md
| 1 | # Weekly Review |
| 2 | |
| 3 | Produce a terse end-of-week summary that captures what changed and what is still owed. |
| 4 | |
| 5 | ## Steps |
| 6 | |
| 7 | 1. **Determine the Week.** Confirm the ISO week (e.g. `2026-W21`). Use `date` or the `inject-now` hook. |
| 8 | |
| 9 | 2. **Gather inputs.** Read: |
| 10 | - `vault/Daily/` — all daily notes from Monday through today (or the last 7 days). Pull `## Priorities`, `## Completed`, and any `## Reflection` sections. |
| 11 | - `vault/Decisions/` — any decision records dated this week. |
| 12 | - `memory/topics/` — entries modified this week (check `memory/MEMORY.md` for the index). |
| 13 | - If meeting notes exist in `vault/`, scan recent ones for open action items. |
| 14 | |
| 15 | 3. **Synthesize five sections:** |
| 16 | |
| 17 | - **Done** — what was completed (shipped, merged, decided, closed). |
| 18 | - **Slipped** — what was planned but not done; carry-forward items. |
| 19 | - **Decisions** — key decisions made (link to `vault/Decisions/` files). |
| 20 | - **Owed to others** — commitments the user owes to someone else. |
| 21 | - **Owed to self** — commitments the user made to themselves. |
| 22 | |
| 23 | 4. **Propose top 3 priorities for next week.** Base them on the slip-list and the most consequential pending commitments. One sentence each. |
| 24 | |
| 25 | 5. **Write to vault** (optional). Ask the user; if they approve, write to `vault/Weekly/YYYY-WW.md`. |
| 26 | |
| 27 | ## Output |
| 28 | |
| 29 | Lead with one sentence summarising the week. Then: |
| 30 | |
| 31 | ``` |
| 32 | ## Weekly Review — YYYY-WW |
| 33 | |
| 34 | **Done** |
| 35 | - ... |
| 36 | |
| 37 | **Slipped** |
| 38 | - ... |
| 39 | |
| 40 | **Decisions** |
| 41 | - ... |
| 42 | |
| 43 | **Owed to others** |
| 44 | - ... |
| 45 | |
| 46 | **Owed to self** |
| 47 | - ... |
| 48 | |
| 49 | ### Next week's top 3 |
| 50 | 1. ... |
| 51 | 2. ... |
| 52 | 3. ... |
| 53 | ``` |
| 54 | |
| 55 | Terse and scannable. Omit any empty section. End with no closing line. |
People who liked this also viewed
6 picksType
- lark-workflow-meeting-summary会议纪要整理工作流：汇总指定时间范围内的会议纪要并生成结构化报告。当用户需要整理会议纪要、生成会议周报、回顾一段时间内的会议内容时使用。SkillsJul 2026
- lark-workflow-standup-report日程待办摘要：编排 calendar +agenda 和 task +get-my-tasks，生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。SkillsJul 2026
- lark-approval飞书审批：查询和处理审批待办/已办/实例，搜索可发起审批定义、查看定义详情并发起原生审批实例。当用户要处理审批任务、查看审批实例、搜索或发起审批时使用。审批待办不是飞书任务；非审批类待办走 lark-task。不负责创建审批定义；三方审批定义不走原生提单。SkillsJul 2026
- lark-okr飞书 OKR：管理目标与关键结果。查看和编辑 OKR 周期、目标、关键结果、对齐关系、量化指标和进展记录。当用户需要查看或创建 OKR、管理目标和关键结果、查看对齐关系时使用。不负责：待办任务管理（lark-task）、日程/会议安排（lark-calendar）、绩效评估SkillsJul 2026
- brainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.SkillsJul 2026
- simpleInvoke before any creative or architectural work — feature design, component creation, or behavioral changes. A streamlined brainstorming process optimized for fast, focused decision-making. Gen AgentSkillsMar 2026
