Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-14 | ✗→✓ | ▲ Improved | -34% | 0% |
| case-16 | ✗→✓ | ▲ Improved | 59% | 0% |
| case-05 | ✓→✗ | ▼ Worse | -60% | 0% |
| case-11 | ✓→✗ | ▼ Worse | -69% | 0% |
| case-12 | ✓→✗ | ▼ Worse | 63% | 0% |
<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> @${CLAUDE_PLUGIN_ROOT}/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 @${CLAUDE_PLUGIN_ROOT}/workflows/forensics.md end-to-end. </process>
<success_criteria>
.planning/forensics/report-{timestamp}.md</success_criteria>
<critical_rules>
</critical_rules>
Other measured skills in the registry, with their headline benchmark lift.