gsd-forensics

Diagnose a failed git workflow by analyzing git history, planning artifacts, and filesystem state to detect anomalies. The investigation reconstructs events from observable facts like git log diffs and state files to identify what went wrong.

Workflow forensics is the investigation of failure patterns like stuck loops, missing artifacts, and abandoned work in multi-step executions. You need an incident report when a GSD workflow crashes or stops unexpectedly and requires evidence-based troubleshooting.

Generate a post-mortem report by running a forensics analysis that checks for crash patterns and missing artifacts across git history and `.planning/` state files. The process outputs a structured report written directly to the `.planning/forensics/` directory.

Yes, you can investigate missing planning artifacts by checking the filesystem state and analyzing `.planning/STATE.md` along with phase directories. The anomaly-driven investigation detects abandoned work and outputs findings with optional issue-creation prompts.

The best way to find interruption evidence is to reconstruct the execution timeline from git log and session-level report files. This anomaly detection approach identifies crash patterns and abandoned work by grounding findings in observable repository facts.

Forensic workflow analysis requires no external dependencies, relying entirely on native git commands and local `.planning/` directory artifacts. It operates directly within your existing repository environment to gather evidence from unmodified state files.