coco-research/gsd-forensics
Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong
npx skills add https://github.com/coco-research/coco --skill gsd-forensics
<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.
</objective>
<execution_context>
@$HOME/.claude/get-shit-done/workflows/forensics.md
</execution_context>
<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:
</context>
<process>
Read and execute the forensics workflow from @$HOME/.claude/get-shit-done/workflows/forensics.md end-to-end.
</process>
<success_criteria>
.planning/forensics/report-{timestamp}.md</success_criteria>
<critical_rules>
</critical_rules>
Take coco-research/gsd-forensics from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.