Back to Details

weekly-debrief

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/weekly-debrief — 週報

/weekly-debrief — Weekly Report

把一週的日報收斂成一頁:主線、趨勢、reflection。只讀 
journal/daily/
的 7 份 md —— 便宜、快,且不受 transcript 保留期影響。
🤖 R2-D2 時刻:一次任務是一筆記錄,一場戰役是七筆記錄的樣子 —— 看得出補給線問題的,從來是後者。
Condense a week of daily reports into one page: main threads, trends, reflection. Only read the 7 md files under 
journal/daily/
— cheap, fast, and unaffected by transcript retention.
🤖 R2-D2 moment: a single mission is one record; a campaign is what seven records look like — the one who can see supply-line problems is always the latter.

用法

Usage

/weekly-debrief [週]
—— 不帶參數＝本週(到目前);
last
＝上週;
YYYY-Www
＝指定週;給任一 
YYYY-MM-DD
＝該日所在的週。週一起算。
/weekly-debrief [week]
— no argument = current week (up to now); 
last
= previous week; 
YYYY-Www
= specified week; any 
YYYY-MM-DD
= the week containing that day. Weeks start on Monday.

動作

Actions

  1. 盤點該週 7 天的日報檔(
    journal/daily/
    ):
    • 缺的日子、且仍在 transcript 保留期內 → 先照 /daily-debrief 的流程補生成(自癒);
    • 真的無料可補 → 週報裡標「X/X 無記錄(超出保留期)」,不裝沒事。
  2. 寫週報,只依 7 份日報、模板如下:
    markdown
    # YYYY-Www 週報(MM-DD ~ MM-DD)
## 本週主線
- <跨多日的工作線,含起訖與結果>
## 數字與趨勢
總 sessions/tokens|最花 token 的專案|與上週比(若上週檔在)
## Reflection
- 這週最值得留的一課:
- 重複出現的卡點:
- 下週優先:
  3. 落地並驗證:寫入 
    journal/weekly/YYYY-Www.md
    後回讀確認。
  4. 同場寫通知摘要 
    journal/weekly/YYYY-Www.digest.txt
    (純文字零 markdown,格式同 daily-debrief 第 5 步,sessions 列表換成「每日一行」)。
  5. 產出後動作(選配):同 daily-debrief,存在 
    config.env
    就執行 
    JOURNAL_POST_CMD
    ,連結放訊息最上面。
  6. 對話內回報:同 daily-debrief 第 7 步,完整報告網址以裸連結貼出。
  1. Inventory the 7 daily report files for that week (
    journal/daily/
    ):
    • If a day is missing and still within the transcript retention window → generate it first via the /daily-debrief flow (self-healing);
    • If there is genuinely nothing to backfill → mark "X/X no record (beyond retention)" in the weekly report, don't pretend it's fine.
  2. Write the weekly report, based only on the 7 daily reports, with the following template:
    markdown
    # YYYY-Www 週報(MM-DD ~ MM-DD)
## 本週主線
- <跨多日的工作線,含起訖與結果>
## 數字與趨勢
總 sessions/tokens|最花 token 的專案|與上週比(若上週檔在)
## Reflection
- 這週最值得留的一課:
- 重複出現的卡點:
- 下週優先:
  3. Save and verify: write to 
    journal/weekly/YYYY-Www.md
    , then read it back to confirm.
  4. Also write a notification digest 
    journal/weekly/YYYY-Www.digest.txt
    (plain text, zero markdown, same format as step 5 of daily-debrief, but with the sessions list replaced by "one line per day").
  5. Post-generation action (optional): same as daily-debrief, if 
    config.env
    exists execute 
    JOURNAL_POST_CMD
    , put the link at the very top of the message.
  6. Report in conversation: same as step 7 of daily-debrief, post the full report URL as a bare link.

鐵律

Iron Rules

  • ✅ 只讀日報 md:原始 transcript 與 raw 骨架都不碰;日報寫錯就先修日報再重跑週報。
  • 🔁 冪等:任一週可重生;缺口自癒優先於報錯。
  • 🚫 趨勢要有兩點才叫趨勢:上週檔不存在就不寫「比上週」,不假造基準。
  • ✅ Only read daily report md: never touch raw transcripts or raw skeleton; if a daily report is wrong, fix the daily report first, then rerun the weekly report.
  • 🔁 Idempotent: any week can be regenerated; self-healing gaps takes priority over erroring out.
  • 🚫 Two points make a trend: if last week's file doesn't exist, don't write "compared to last week", don't fabricate a baseline.