菜单
Mandatory weekly signal. Generates the weekly-review briefing with proposed closures, promotions, and cleanup. Active from week 1 — the bridge skill between onboarding and steady state. Run at start or end of week, or whenever it's been more than 6 days since the last one.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Process unprocessed transcripts in system/intake/ into atlas/meetings, atlas/decisions, atlas/people updates, and gtd/inbox proposals. Uses Gemini 3.1 Flash Lite as the structured extractor (~$0.002/transcript, 4s latency) and Claude for vault integration (wikilink resolution, matching cross-updates, file ops, verification). Operator-confirmed per transcript. Honors matching, action-item ownership, source-documentation, and the source-processing-pattern intake → process → archive flow.
Pull raw verbatim transcripts from Granola (meetings, notes, phone calls), Google Meet standalone Transcript Docs, AND the verbatim Transcript tab inside "Notes by Gemini" Docs — into system/intake/ via three ETL scripts. Pure script orchestration — no AI synthesis, no tokens spent on extraction. Idempotent (skips already-pulled). Default lookback 7 days; flags for 14d / backfill / dry-run / status / single-source. Use when the operator says "get transcripts", "pull transcripts", "grab the last N days of transcripts", or before /process-transcripts.
Unpack complex work or a dense topic one idea at a time, checking comprehension at each step rather than delivering a wall of text. Use when the operator asks to "unpack", be "caught up", or "walked through" something — and offer it proactively before any recap, plan, or explanation long enough to overwhelm in a single message.
Owner-only release management for WorkDesk OS at BenaliHQ/workdesk-os. Pre-merge gate, release cut via scripts/release.sh, post-release smoke test against a pinned canary vault, and rollback. Use ANY time work is being landed into the workdesk-os repo or a release is being cut — downstream operators receive these changes via /update. Trigger phrases — "add this to workdesk", "get this into workdesk", "merge this to workdesk", "ship this to workdesk", "land this in workdesk", "cut a workdesk release", "release workdesk os", "tag a workdesk release", "smoke the workdesk release", "rollback the workdesk release". Also auto-trigger when working in /Users/khalilbenali/code/workdesk-os and the operator says anything about merging, shipping, releasing, or landing changes. Owner-only — not for downstream operators.
Safely start, resume, inspect, and finish isolated repo work when the operator says "work on <repo>", "start working on", "pick up <task>", "parallel session", "is anyone else working on", or "hand this off / I'm done with this task".
Plan, organize, and pressure-test multi-step projects with the GTD Natural Planning Model. A skill family: `/pobo` (guided plan), `/pobo organize` (restructure a brief/brainstorm into clean phases), `/pobo review` (adversarially pressure-test a plan). Use `/pobo --lite` for fast low-stakes planning.
| name | weekly-review |
| description | Mandatory weekly signal. Generates the weekly-review briefing with proposed closures, promotions, and cleanup. Active from week 1 — the bridge skill between onboarding and steady state. Run at start or end of week, or whenever it's been more than 6 days since the last one. |
The most important signal in the first 30 days. Active from week 1. Stable everyday loop ships before vault-improvements ever runs.
/weekly-review — full cycle/weekly-review --preview — show proposed closures/promotions without writing inbox itemsPer config/signals/weekly-review.md:
gtd/actions/next/ and gtd/actions/waiting/ (status, last-touched)gtd/projects/*/_status.md (active, expected-cadence vs last-touched)gtd/recurring/schedules/ filter status: active AND next_due <= today + 7dgtd/inbox/ (full backlog + age + prefix mix)gtd/projects/*) and stale recurring items (gtd/recurring/*): today - last-touched > 1.5 × expected-cadence (skip expected-cadence: none)personal/daily/ (read only)weekly-review.last-firedBuild sections:
gtd/archive/actions/{current-month}/, archived projects, decisions logged, content publishedwaiting: >7 days), inbox backlogintel/briefings/weekly/{YYYY-MM-DD}-weekly-review.md:
---
type: signal
shape: briefing
date: 2026-04-26
sources: [...]
schedule: weekly
week-of: 2026-04-20
---
[REVIEW] itemsFor each proposed closure/promotion, drop a [REVIEW] item in gtd/inbox/:
waiting/ for 9 days — chase, close, or move to someday/?"weekly-payroll due tomorrow — promote to next?"Subject to flood guard (≤7 per session — additional candidates batched).
After successful write:
config/state/signals.json → weekly-review.last-fired = todayIf all three are true:
phases.graduation: completeThen update config/operator-profile.md first-30-days-mode: graduated and tell the operator: "You've graduated from first-30-days. Vault-improvements activates in {X} days."
[REVIEW] items in one session. Batch the rest.