gsd-forensics

To investigate a stuck workflow execution, analyze repository state, commit history, and `.planning/` artifacts to detect anomalies. Collect read-only evidence from `git log`, `git status`, and plan files to identify interrupted sessions or missing artifacts, then generate a structured diagnostic report.

Missing or inconsistent planning files during a post-mortem analysis are caused by interrupted sessions, stuck loops, or abandoned work. Checking `.planning/` state files alongside `git diff` reveals crash patterns and anomalous execution phases that leave artifacts incomplete.

Diagnose interrupted GSD sessions by pulling signals from `git log`, `git status`/`git diff`, and `.planning/` state files. This evidence-driven approach detects stuck loops, abandoned work, and crash patterns without guessing, producing a timestamped forensic report.

Forensic workflow analysis does not require write access to the repository. It relies on read-only evidence collection from git history and `.planning/` files, redacts sensitive data, and writes the output report safely under `.planning/forensics/`.

The best way to document post-mortem findings for incident analysis is to save a structured forensic report under `.planning/forensics/`. This report presents findings inline and offers deeper interactive investigation plus optional issue creation for tracking.

Your workflow gets stuck in a loop and leaves abandoned planning artifacts due to crash or interruption patterns during execution phases. Analyzing `.planning/` state files and `git status` reveals these anomalies and helps pinpoint the exact failure point.