Diagnose failed workflow root causes

Diagnose failed GSD workflows via git history and artifact analysis

Understanding why a GSD workflow got stuck or failed, with data-grounded diagnostic findings rather than speculation.

• · Problem description (optional, will ask if not provided)

• · Forensic report saved to .planning/forensics/report-{timestamp}.md
• · Findings, anomalies, recommendations inline
• · Optional GitHub issue with redacted sensitive data

• · forensics.md workflow
• · git history, .planning/ artifacts

• · Project has .planning/ directory with STATE.md and phases/
• · Git history available for analysis

• · Insufficient data in artifacts → findings incomplete
• · Git history too old → relevant commits missing
• · Sensitive data present → must redact before output
• · Anomalies found but root cause unclear → mark as insufficient evidence

• · Evidence-grounded findings (git commits, file state, STATE.md)
• · No speculation without evidence
• · Redaction of sensitive data built-in
• · 4+ anomaly types checked: stuck loop, missing artifacts, abandoned work, crash/interruption