Prompt file imported from buslam2005/finallytwo (
.claude/commands/gsd-forensics.md). Fill in{{arguments}}before use. Copyright stays with the author.
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.
<execution_context> @/Users/andrewlam/finally2/finally/.claude/gsd-core/workflows/forensics.md </execution_context>
User input:
- Problem description: {{arguments}} (optional — will ask if not provided)
<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>