Skill
gsd-forensics
Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong
Trigger Phrases
No trigger phrases were parsed from this skill.
Structured Sections
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: $ARGUMENTS (optional — will ask if not provided)
Process
Read and execute the forensics workflow from @$HOME/.Codex/get-shit-done/workflows/forensics.md end-to-end.
Objective
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.