juaniitos/gsd-forensics
.agent/skills/gsd-forensics/SKILL.md
Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong
data-ai
Updated Apr 16, 2026
$ install --global
skillsauthnpx skillsauth add juaniitos/anyone-ai-interviewer-frontend gsd-forensicsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 4:39 PM6.4s1 file scanned
SKILL.md
- name:
- gsd-forensics
- description:
- Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong
<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> @.agent/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:
- Problem description: $ARGUMENTS (optional — will ask if not provided) </context>
<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
juaniitos/gsd-workstreams
tools
VerifiedTrustedCommunity
Manage parallel workstreams — list, create, switch, status, progress, complete, and resume
SKILL.mdUpdated Apr 17, 2026
juaniitos/gsd-verify-work
testing
VerifiedTrustedCommunity
Validate built features through conversational UAT
SKILL.mdUpdated Apr 17, 2026
juaniitos/gsd-validate-phase
testing
VerifiedTrustedCommunity
Retroactively audit and fill Nyquist validation gaps for a completed phase
SKILL.mdUpdated Apr 17, 2026
juaniitos/gsd-update
testing
VerifiedTrustedCommunity
Update GSD to latest version with changelog display
SKILL.mdUpdated Apr 17, 2026