gsd-forensics

Name: gsd-forensics
Availability: InStock
Author: duyseu

Analyze git history and planning state to diagnose GSD workflow failures.

1|Updated Aug 17, 2025

Search Tags:#git #workflow #planning #diagnostics #root-cause #forensics

Ready to run

npx skills add https://github.com/DuySeu/StockMind --skill gsd-forensics-duyseu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-forensics
Source: https://github.com/DuySeu/StockMind/tree/main/.agent/skills/gsd-forensics
Command: npx skills add https://github.com/DuySeu/StockMind --skill gsd-forensics-duyseu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-mortem investigation for failed GSD workflows — analyzes git history, artifacts, and state to diagnose what went wrong

Core Features & Use Cases

Evidence gathering from multiple data sources (git log, git status, .planning/STATE.md, .planning/ROADMAP.md, and .planning/phases/*/).
Detects anomalies across common failure modes (stuck workflows, missing artifacts, abandoned work sessions, crashes).
Generates a structured forensic report written to .planning/forensics/report-{timestamp}.md with inline findings and optional GitHub issue creation.

Quick Start

Run the forensics workflow to generate a diagnostic report saved to .planning/forensics/report-<timestamp>.md

Frequently Asked Questions about gsd-forensics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I diagnose a failed git workflow and find the root cause of missing artifacts?▼

To diagnose a failed git workflow and find root causes, you analyze git history, session state, and planning artifacts to detect anomalies like missing files or unexpected state transitions, generating a structured forensic report.

What is the best way to investigate stuck GSD planning phases and unexpected state transitions?▼

The best way to investigate stuck planning phases and unexpected state transitions is to cross-reference git logs with .planning/STATE.md and .planning/ROADMAP.md files to pinpoint where the workflow deviated from expected execution states.

Do I need specific file formats or directories to run a git history forensics analysis?▼

Yes, running a git history forensics analysis requires access to git logs, .planning/* files including STATE.md and ROADMAP.md, and session state data to accurately identify root causes of workflow failures.

Does post-mortem workflow investigation support non-destructive reporting and sensitive data redaction?▼

Yes, post-mortem workflow investigation ensures non-destructive reporting and redacts sensitive information while generating diagnostic reports saved to .planning/forensics/report-{timestamp}.md with optional GitHub issue creation.

How do I generate a diagnostic report for abandoned work sessions and crashes?▼

You generate a diagnostic report for abandoned work sessions and crashes by analyzing evidence from git status and .planning/phases/*/ directories to detect anomalies, outputting inline findings to a timestamped markdown file.