gsd-forensics

To diagnose a failed GSD workflow, collect git logs, diffs, and .planning artifacts to detect anomalies like stuck loops or inconsistent state transitions. The investigation produces an evidence-backed timeline citing specific commits and files to explain the root cause.

Post-mortem analysis for git workflows examines repository history and workspace file state to classify failure modes like abandoned work or execution crashes. It produces an auditable, timestamped forensic report detailing anomalies and recommended fixes.

Find missing .planning artifacts by scanning the repository for STATE.md and phase artifacts, then cross-referencing them against git logs and diffs. This detects inconsistent state transitions and abandoned work while citing specific files as evidence.

Yes, you can automatically propose creating a GitHub issue when the forensic investigation identifies actionable findings. The report generated from git history and workspace state offers interactive next steps, including optional issue creation for remediation tracking.

Workflow diagnostics require no external dependencies but must run on repositories containing .planning artifacts, git history, and workspace file state. It operates directly on this local data to detect anomalies and save timestamped reports.

Yes, sensitive data is redacted before saving the timestamped forensic report to the .planning/forensics/ directory. This ensures the generated incident response documentation remains safe and auditable without exposing confidential repository information.