Back to Details

retro

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

/retro

/retro

Capture implementation feedback for future grooming sessions.
捕获实现阶段的反馈，用于后续的需求梳理会议。

Philosophy

设计理念

When implementation reveals that an issue was underscoped, that signal should persist. 
/retro
captures these signals so 
/groom
can adjust future scoping.
当实现过程暴露出需求存在范围定义不足的问题时，这个信号应该被保留下来。
/retro
负责捕获这些信号，以便
/groom
能够调整未来的需求范围定义。

Storage

存储位置

{repo}/.groom/retro.md
Created automatically if missing. Appended to, never overwritten.
{repo}/.groom/retro.md
如果文件不存在会自动创建。仅追加内容，不会覆盖原有内容。

Format

格式

markdown
undefined
markdown
undefined

Implementation Retrospective

Implementation Retrospective

Entry: #{issue} — {title} ({date})

Entry: #{issue} — {title} ({date})

Effort: predicted {predicted} → actual {actual} Scope changes: {what changed from original issue} Blockers: {what blocked progress} Pattern: {reusable insight for future scoping}
undefined
Effort: predicted {predicted} → actual {actual} Scope changes: {what changed from original issue} Blockers: {what blocked progress} Pattern: {reusable insight for future scoping}
undefined

Subcommands

子命令

/retro append

/retro append

Interactive capture. Ask:
  1. Which issue did you just finish? (issue number)
  2. What was the predicted effort? (from effort label)
  3. What was the actual effort?
  4. Did scope change during implementation? How?
  5. What blocked you?
  6. What should future grooming sessions know?
Then append to 
{repo}/.groom/retro.md
.
交互式捕获流程。会询问以下问题：
  1. 你刚完成的是哪个需求？（需求编号）
  2. 预估的工作量是多少？（来自工作量标签）
  3. 实际工作量是多少？
  4. 实现过程中需求范围是否有变更？具体是怎样的？
  5. 你遇到了哪些阻塞？
  6. 后续的需求梳理会议需要了解哪些信息？
之后将内容追加到
{repo}/.groom/retro.md
中。

Automated Append (from /done and /pr)

自动追加（来自/done和/pr）

When invoked programmatically by 
/done
or 
/pr
, accept structured data:
/retro append --issue 42 --predicted m --actual l --scope "Added retry logic not in original spec" --blocker "Webhook signature verification undocumented" --pattern "Webhook issues always need retry logic"
Append without interactive prompts.
当被
/done
或
/pr
以编程方式调用时，接受结构化数据：
/retro append --issue 42 --predicted m --actual l --scope "Added retry logic not in original spec" --blocker "Webhook signature verification undocumented" --pattern "Webhook issues always need retry logic"
无需交互式提问，直接追加内容。

How /groom Uses Retro

/groom如何使用Retro数据

During Phase 1, 
/groom
reads 
retro.md
and extracts patterns:
  • Effort calibration: "Payment issues consistently take 1.5x estimates"
  • Scope patterns: "Webhook issues always need retry logic added during implementation"
  • Blocker patterns: "External API docs are frequently wrong — always verify with web research"
  • Domain insights: "Bitcoin wallet issues require manual testing on regtest"
These patterns inform:
  • Effort estimates (adjust based on historical accuracy)
  • Issue scoping (include commonly-missed concerns upfront)
  • Boundary statements (prevent known scope creep patterns)
  • Research priorities (investigate known problem areas proactively)
在第一阶段，
/groom
会读取
retro.md
并提取模式：
  • 工作量校准： "支付相关需求的实际耗时始终是预估的1.5倍"
  • 范围模式： "Webhook相关需求在实现过程中总是需要添加重试逻辑"
  • 阻塞模式： "外部API文档经常出错——务必通过网络调研进行验证"
  • 领域洞察： "比特币钱包相关需求需要在regtest环境下进行手动测试"
这些模式会用于：
  • 工作量估算（根据历史准确性进行调整）
  • 需求范围定义（提前纳入常见的遗漏点）
  • 边界声明（防止已知的范围蔓延模式）
  • 研究优先级（主动调研已知的问题领域）

Related

相关工具

  • /done
    — Appends retro signals after session retrospective
  • /pr
    — Appends retro signals when opening PR
  • /groom
    — Reads retro.md during Phase 1 (Context)
  • /done
    — 会话回顾后追加Retro信号
  • /pr
    — 提交PR时追加Retro信号
  • /groom
    — 在第一阶段（上下文阶段）读取retro.md