菜单
Read all session debriefs, synthesize patterns, and produce a retrospective. Use when the user says "/session:retro", "retrospective", "session retro", "what patterns do we see", "synthesize debriefs", or "review all debriefs".
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Session dashboard showing thread timeline, agent roster, and commit counts. Use when the user says "/session:dashboard", "show dashboard", "session overview", "session summary", "what's happening in this session", or "agent activity".
Write a reflective debrief for a session thread. Use when closing a thread, after "/session:debrief", "/debrief", "write a debrief", "debrief this thread", or when session:thread:land invokes it after the done verdict passes.
Manage sessions, threads, and session wiring. Use when the user mentions sessions, threads, plans, reviews, claims, debriefs, or session sync/doctor. Also triggered by natural language like "create a thread", "what threads are open", "close this thread", "show me the session", "sync the session", "check session health", "claim the frontend thread", "lock the plan", "add a task", or "what's the session status".
Structured context brief and claim transfer for thread handoff between agents. Use when the user says "/session:thread:handoff", "/thread:handoff", "hand off this thread", "transfer thread to", "pass this to another agent", "handoff", or "take over thread".
Perform a real closeout audit for the thread-scoped task and, when requested, land it through commit, push, and CI. Use when the user says "/session:thread:land", "are you done", "can we close this", "is anything still open", "wrap this session up", or wants to end the thread without losing unfinished work, buried follow-ups, or useful loose ends.
| name | session_retro |
| description | Read all session debriefs, synthesize patterns, and produce a retrospective. Use when the user says "/session:retro", "retrospective", "session retro", "what patterns do we see", "synthesize debriefs", or "review all debriefs". |
| argument-hint | [focus area] |
Read all debriefs in the current session and synthesize a retrospective.
~/.claude/skills/session/scripts/session.sh status to get the session directory.debrief.md files in both active (thread.*/debrief.md) and done (done.thread.*/debrief.md) thread directories.Write to .session/retro.md:
# Retrospective: <session_key>
Generated: <ISO timestamp>
Debriefs analyzed: <count>
## Patterns
Recurring themes, approaches, or decisions across threads.
## What Worked
Techniques, tools, or decisions that debriefs consistently praised.
## What Didn't Work
Friction points, mistakes, or blockers that appeared across threads.
## Recommendations
Concrete suggestions for future sessions based on the patterns above.
If the user provides a focus area (e.g., "testing", "coordination"), weight the synthesis toward that topic while still covering the full picture.
If no debrief files exist, say so and suggest running /debrief on completed threads.