一键导入
retro
Session retrospective. Use when the user asks to reflect on the conversation, do a retro, or introspect the session.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Session retrospective. Use when the user asks to reflect on the conversation, do a retro, or introspect the session.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Fetch origin/main and rebase the current worktree or branch onto the latest origin/main.
Move a sibling worktree's branch into the main checkout, then remove the worktree.
Fix or build the requested change in a git worktree, then open a PR.
Review code changes in the current branch for issues
Convert a plan into a beads epic with detailed issues and subissues
Investigate a GitHub issue or feature description, determine status, and plan implementation if needed
| name | retro |
| description | Session retrospective. Use when the user asks to reflect on the conversation, do a retro, or introspect the session. |
| user-invocable | true |
| disable-model-invocation | true |
Reflect on this conversation from start to finish. Be honest, specific, and constructive. Address each section below.
Identify specific moments, approaches, or tool uses in this session that were effective. Reference concrete examples from the conversation.
Identify missteps, wasted effort, wrong turns, or inefficiencies. Be specific about what happened and why it was suboptimal.
Based on this session, suggest specific improvements to:
Provide observations about the user's work style that affected the session:
List important questions that came up (explicitly or implicitly) during this session that the user never answered. These are questions whose answers would have meaningfully changed the approach or outcome.
Be direct and concise. Use bullet points. No fluff or generic advice — every point should reference something specific from this session.