Back to Details

recap

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

MANDATORY PREPARATION

必备准备工作

Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.
Get back up to speed fast. Recap reads the most recent session file and recent decisions to tell you where you left off and what to do next.
调用/agent-workflow——其中包含工作流原则、反模式以及上下文收集协议。在继续操作前请遵循该协议——如果还没有工作流上下文，你必须先运行/teach-maestro。
快速恢复工作进度。Recap功能会读取最新的会话文件和近期决策，告知你上次的工作进度以及后续操作。

Data Sources

数据来源

  1. .maestro/sessions/
     — read the most recent session file (by filename date)
  2. .maestro/decisions.jsonl
     — read the last 5 decisions
If no session files exist, read the last 10 decisions and summarize those instead.
If no data exists at all, respond: "No session history found. Run 
/capture
at the end of your next session to start tracking."
  1. .maestro/sessions/
     — 读取最新的会话文件（按文件名日期排序）
  2. .maestro/decisions.jsonl
     — 读取最近5条决策
如果不存在会话文件，则读取最近10条决策并进行总结。
如果完全没有数据，请回复："未找到会话历史记录。请在下次会话结束时运行
/capture
开始跟踪。"

Output Format

输出格式

text
┌─────────────────────────────────────┐
│         LAST SESSION RECAP          │
├─────────────────────────────────────┤
│ Date: YYYY-MM-DD                    │
│ Commands: /diagnose → /fortify (2)  │
│ Files: 3 changed, 1 created        │
│ Outcome: Completed                  │
├─────────────────────────────────────┤
│ PICK UP HERE:                       │
│ 1. Run /guard — rate limiting       │
│ 2. Run /evaluate — adversarial tests│
└─────────────────────────────────────┘
text
┌─────────────────────────────────────┐
│         LAST SESSION RECAP          │
├─────────────────────────────────────┤
│ Date: YYYY-MM-DD                    │
│ Commands: /diagnose → /fortify (2)  │
│ Files: 3 changed, 1 created        │
│ Outcome: Completed                  │
├─────────────────────────────────────┤
│ PICK UP HERE:                       │
│ 1. Run /guard — rate limiting       │
│ 2. Run /evaluate — adversarial tests│
└─────────────────────────────────────┘

Recap Rules

Recap规则

  • Be concise — this is a 30-second read, not a report
  • Lead with the "PICK UP HERE" section — that's what the user needs
  • If the session ended with open issues, highlight them
  • Reference specific files and commands, not vague summaries
  • 简洁明了——这是30秒就能读完的内容，不是正式报告
  • 以“PICK UP HERE”部分开头——这是用户最需要的信息
  • 如果会话结束时存在未解决问题，需突出显示
  • 引用具体的文件和命令，避免模糊总结

Recap Checklist

Recap检查清单

  • Most recent session identified
  • Commands and outcomes summarized in one line each
  • "Pick up here" section has specific, actionable next steps
  • Open issues from last session surfaced
  • 已识别最新会话
  • 命令和结果各用一句话总结
  • “Pick up here”部分包含具体、可执行的后续步骤
  • 已列出上一环节的未解决问题

Recommended Next Step

推荐后续步骤

After recapping, run the first command listed in "Pick Up Here" to continue where you left off.
NEVER:
  • Dump the entire session file — summarize it
  • Recap without checking decisions.jsonl for recent activity
  • Give vague next steps ("continue working") — be specific
  • Assume context from the current conversation — only use persisted data
完成总结后，运行“Pick Up Here”中列出的第一个命令，继续上次的工作。
绝对不要：
  • 直接输出整个会话文件——要进行总结
  • 未检查decisions.jsonl中的近期活动就进行总结
  • 给出模糊的后续步骤（如“继续工作”）——必须具体
  • 假设当前对话中的上下文——仅使用持久化数据