davepoon/buildwithclaude / plugins/gsd/skills/forensics
gsd:forensics
VerifiedPost-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong
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> @${CLAUDE_PLUGIN_ROOT}/workflows/forensics.md </execution_context>
User input:
- Problem description: $ARGUMENTS (optional — will ask if not provided)
<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>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |