gsd-forensics

To find the root cause of a failed Git workflow, analyze repository state, git history, and planning artifacts. This diagnostic process identifies anomalies like stalled flows and state inconsistencies to generate evidence-backed remediation reports.

Post-mortem diagnostics for stalled workflows is the structured investigation of repository state and session history. It detects missing artifacts and state inconsistencies to produce actionable remediation guidance for failed projects.

Yes, analyzing session state requires a .planning directory. The forensic analysis applies to projects with .planning directories, git history, and session state to accurately track structured state and identify workflow anomalies.

To generate a diagnostic report from planning artifacts, run the forensics analysis on the current project. It processes existing workflow state, detects anomalies, and outputs structured forensic reports with optional issue creation steps.

Yes, you can redact sensitive data in root-cause-analysis reports. The forensic reporting process meets requirements for evidence-backed reporting and sensitive data redaction to safely support remediation efforts.