name	gsd-forensics
description	Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong

Investigate what went wrong during a GSD workflow execution. Analyzes git history, `.planning/` artifacts, and file system state to detect anomalies and generate a structured diagnostic report.

Purpose: Diagnose failed or stuck workflows so the user can understand root cause and take corrective action. Output: Forensic report saved to .planning/forensics/, presented inline, with optional issue creation.

<execution_context> @C:/Work/Code/kylin-router/.trae/get-shit-done/workflows/forensics.md </execution_context>

**Data sources:** - `git log` (recent commits, patterns, time gaps) - `git status` / `git diff` (uncommitted work, conflicts) - `.planning/STATE.md` (current position, session history) - `.planning/ROADMAP.md` (phase scope and progress) - `.planning/phases/*/` (PLAN.md, SUMMARY.md, VERIFICATION.md, CONTEXT.md) - `.planning/reports/SESSION_REPORT.md` (last session outcomes)

User input:

Problem description: {{GSD_ARGS}} (optional — will ask if not provided)

Read and execute the forensics workflow from @C:/Work/Code/kylin-router/.trae/get-shit-done/workflows/forensics.md end-to-end.

<success_criteria>

Evidence gathered from all available data sources
At least 4 anomaly types checked (stuck loop, missing artifacts, abandoned work, crash/interruption)
Structured forensic report written to .planning/forensics/report-{timestamp}.md
Report presented inline with findings, anomalies, and recommendations
Interactive investigation offered for deeper analysis
GitHub issue creation offered if actionable findings exist </success_criteria>

<critical_rules>

Read-only investigation: Do not modify project source files during forensics. Only write the forensic report and update STATE.md session tracking.
Redact sensitive data: Strip absolute paths, API keys, tokens from reports and issues.
Ground findings in evidence: Every anomaly must cite specific commits, files, or state data.
No speculation without evidence: If data is insufficient, say so — do not fabricate root causes. </critical_rules>