How do I install the Gsd Forensics skill?

Run npx skillmds@latest add lgwanai/gsd-forensics in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Gsd Forensics skill do?

Post-mortem investigation for failed GSD workflows — diagnoses what went wrong. It is listed under Coding & Dev Tools on SkillMD.

Is Gsd Forensics safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Gsd Forensics?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Gsd Forensics free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Gsd Forensics?

lgwanai (@lgwanai) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Gsd Forensics by lgwanai — Agent Skill

Name: Gsd Forensics
Author: lgwanai

File contents

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.

User input:

Problem description: $ARGUMENTS (optional — will ask if not provided)

---name: gsd-forensicsdescription: Post-mortem investigation for failed GSD workflows — diagnoses 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>@$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:**- Problem description: $ARGUMENTS (optional — will ask if not provided)</context><process>Execute end-to-end.</process><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>

Frequently asked questions

Gsd Forensics