メニュー
Weekly review — 3-phase process (Collect/Reflect/Plan). Reviews shipped items, blockers, decisions, and plans next week. Use on Fridays or Mondays.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | weekly |
| description | Weekly review — 3-phase process (Collect/Reflect/Plan). Reviews shipped items, blockers, decisions, and plans next week. Use on Fridays or Mondays. |
| allowed-tools | Read, Write, Edit, Bash, Glob, Grep, TaskCreate, TaskUpdate, TaskList, TaskGet |
| user-invocable | true |
Facilitates your weekly review by collecting the past week's data, reflecting on progress, and planning the next week.
Today's date: !date +%Y-%m-%d
Config: @_core/config.yaml Processing logic: @_core/PROCESSING.md
Reference template: @_templates/sprint-retro.md
Create tasks at skill start with dependencies:
TaskCreate: "Phase 1: Collect"
description: "Gather daily notes, shipped items, blockers from past week"
activeForm: "Collecting weekly data..."
TaskCreate: "Phase 2: Reflect"
description: "Analyze patterns, what worked/didn't"
activeForm: "Reflecting on weekly performance..."
TaskCreate: "Phase 3: Plan"
description: "Set next week priorities, identify top risks"
activeForm: "Planning next week..."
Set dependencies:
TaskUpdate: "Phase 2", addBlockedBy: [phase-1-id]
TaskUpdate: "Phase 3", addBlockedBy: [phase-2-id]
Create weekly review note using template:
reports/{date}-sprint-retro.mdSupports --xlsx, --pdf, --pptx flags. See .claude/rules/export-formats.md for layout specs and workflow. Complete normal processing first, then generate the formatted file.
Works with:
/daily - Reviews daily notes from the week/push - Commit after completing review/onboard - Load context for informed review/progress - Detailed project status during reviewPM-Kit command reference and workflow guide. Use for "/help", "what commands are available", "how do I use PM-Kit", "cheat sheet", "show me workflows", or "/help preview" for topic-specific help.
Render vault notes as styled HTML and open in browser. Turn markdown docs, decisions, progress reports into readable previews. Use for "/preview docs/project-a/checkout-flow.md", "/preview progress all", "/preview decide auth-approach", or when user wants to see a doc before sharing.
Executive briefing in plain language — report to me like I'm the CEO or product owner. Business impact and user impact only, no jargon. Use for "/report", "/report project-a", "report to me", "brief me", "what should I know", "executive summary", or when user wants a non-technical status update focused on outcomes not implementation.
Core vault file operations — read/write notes, manage wiki-links, process templates with Handlebars syntax, enforce naming conventions. Auto-invoked for all file operations.
Flag a blocker with severity, owner, and due date. Checks for duplicates before creating. Use for "/block project: description --severity high --due friday".
Log standup update with keyword detection. Multi-project daily notes with auto-blocker/decision detection. Use for "/daily project: shipped X, wip Y, blocked on Z".