Back to Details

gsd-forensics

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<objective> Investigate what went wrong during a GSD workflow execution. Analyzes git history, `.planning/` artifacts, and file system state to detect anomalies and generate a structured diagnostic report.
Purpose: Diagnose failed or stuck workflows so the user can understand root cause and take corrective action. Output: Forensic report saved to 
.planning/forensics/
, presented inline, with optional issue creation. </objective>
<execution_context> @~/.claude/gsd-core/workflows/forensics.md </execution_context>
<context> **Data sources:** - `git log` (recent commits, patterns, time gaps) - `git status` / `git diff` (uncommitted work, conflicts) - `.planning/STATE.md` (current position, session history) - `.planning/ROADMAP.md` (phase scope and progress) - `.planning/phases/*/` (PLAN.md, SUMMARY.md, VERIFICATION.md, CONTEXT.md) - `.planning/reports/SESSION_REPORT.md` (last session outcomes)
User input:
  • Problem description: $ARGUMENTS (optional — will ask if not provided) </context>
<process> Execute end-to-end. </process>
<success_criteria>
  • Evidence gathered from all available data sources
  • At least 4 anomaly types checked (stuck loop, missing artifacts, abandoned work, crash/interruption)
  • Structured forensic report written to 
    .planning/forensics/report-{timestamp}.md
  • Report presented inline with findings, anomalies, and recommendations
  • Interactive investigation offered for deeper analysis
  • GitHub issue creation offered if actionable findings exist </success_criteria>
<critical_rules>
  • Read-only investigation: Do not modify project source files during forensics. Only write the forensic report and update STATE.md session tracking.
  • Redact sensitive data: Strip absolute paths, API keys, tokens from reports and issues.
  • Ground findings in evidence: Every anomaly must cite specific commits, files, or state data.
  • No speculation without evidence: If data is insufficient, say so — do not fabricate root causes. </critical_rules>
<objective> 调查GSD工作流执行过程中出现的问题。分析git历史记录、`.planning/`工件和文件系统状态，以检测异常并生成结构化诊断报告。
目的：诊断失败或停滞的工作流，帮助用户了解根本原因并采取纠正措施。 输出：取证报告保存至
.planning/forensics/
，可在线展示，还可选择创建问题工单。 </objective>
<execution_context> @~/.claude/gsd-core/workflows/forensics.md </execution_context>
<context> **数据源：** - `git log`（近期提交、模式、时间间隔） - `git status` / `git diff`（未提交工作、冲突） - `.planning/STATE.md`（当前位置、会话历史） - `.planning/ROADMAP.md`（阶段范围和进度） - `.planning/phases/*/`（PLAN.md、SUMMARY.md、VERIFICATION.md、CONTEXT.md） - `.planning/reports/SESSION_REPORT.md`（上一会话结果）
用户输入：
  • 问题描述：$ARGUMENTS（可选——若未提供将询问用户） </context>
<process> 端到端执行。 </process>
<success_criteria>
  • 从所有可用数据源收集证据
  • 至少检查4种异常类型（循环停滞、缺失工件、未完成工作、崩溃/中断）
  • 结构化取证报告写入
    .planning/forensics/report-{timestamp}.md
  • 在线展示报告，包含调查结果、异常情况和建议
  • 提供交互式调查以进行深入分析
  • 若发现可执行的结论，提供创建GitHub问题工单的选项 </success_criteria>
<critical_rules>
  • 只读调查： 取证过程中不得修改项目源文件。仅可写入取证报告并更新STATE.md会话跟踪。
  • 敏感数据脱敏： 从报告和问题工单中移除绝对路径、API密钥、令牌。
  • 基于证据得出结论： 每个异常必须引用特定的提交记录、文件或状态数据。
  • 无证据不推测： 若数据不足，需明确说明——不得编造根本原因。 </critical_rules>