gsd-forensics

To diagnose failures in stuck workflow executions, the skill examines git history, project artifacts, and system state to pinpoint the source of problems and generates a structured diagnostic report for recovery.

The best way to recover data after a workflow error or stall is to perform a forensic analysis of your git history and project artifacts, which produces a structured report outlining findings and recommendations for data recovery.

Git history analysis helps troubleshoot complex workflow issues by examining commits and changes to identify discrepancies in the project state, allowing you to trace exactly where the workflow execution encountered errors.

Yes, you need specific project artifacts like the .planning/ directory to diagnose workflow failures. The forensic analysis assesses these artifacts for errors or omissions, alongside reviewing the file system and session history for discrepancies.

Your workflow execution may stall due to errors or omissions in project artifacts or file system discrepancies. You can get a diagnostic report by analyzing your git history and system state to outline findings and recovery recommendations.

Yes, you can use forensic analysis to review session history and file system discrepancies. The diagnostic process evaluates the file system and session logs to identify inconsistencies causing workflow failures.