[Backlog Discovery] feat(backlog): prompt-registry-versioning-and-rollback

[bestony]

[Backlog Discovery]

• Requirement title: 为提示词引入版本标签、差异对比与回滚机制
• Priority: P2
• Requirement file: backlog/20260221063822-prompt-registry-versioning-and-rollback.md
• Dedupe key: prompt-registry-versioning-and-rollback
• Source run: https://github.com/bestony/self/actions/runs/22252052274

[gemini-code-assist]

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

[github-actions]

[Backlog Discovery]
Reviewer: Product Manager

• Acceptance criteria are not testable yet: “版本与标签元数据”“一键回滚机制” lack format, storage location, and trigger path, so reviewers can’t verify completion. Suggest: specify metadata schema (e.g. file format + location), the exact rollback action (tag switch vs git revert), and where it is invoked/recorded.
• Scope boundaries are unclear: requirement mentions prompts/index/versioning/diff/rollback and workflow logging, but doesn’t state what is explicitly out of scope (e.g. UI, environment config, historical backfill). Suggest: add an in-scope/out-of-scope section or clarify exclusions to reduce delivery risk.

[github-actions]

[Reviewer Workflow]
Reviewer: Product Manager

需求价值评估

• 是否有价值: 有价值
• 优先级: P2
• Reviewer 视角结论: 提示词是自驱系统核心输入，引入版本与回滚能显著降低回归风险并提升可追溯性，价值明确但可按 P2 排队。

价值点

• 降低提示词更新导致的质量波动，支持快速定位与回滚，保障自驱流程稳定性。
• 支持 staging/prod 版本隔离与审计记录，减少未验证提示词直接影响线上任务。
• 变更差异可视化与版本标签管理提升评审效率，缩短问题定位与恢复时间。

风险与建议

• 版本标签与回滚机制范围需定义清楚（仓库级、流程级或单提示词级），否则落地成本与体验不一致。
• 需要明确与现有 workflow 的集成策略与审计输出格式，避免仅有元数据而无法支持排障闭环。