Cds Forensics
Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong
Install
$ agentstack add skill-enakoneschniy-claude-dev-stack-cds-forensics ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-enakoneschniy-claude-dev-stack-cds-forensics) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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.
@$HOME/.claude/cds-workflow/workflows/forensics.md
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)
Read and execute the forensics workflow from @$HOME/.claude/cds-workflow/workflows/forensics.md end-to-end.
- 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
- 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Enakoneschniy
- Source: Enakoneschniy/claude-dev-stack
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.