gsd-forensics

Diagnose failed GSD workflow executions by correlating git history and .planning/ artifacts.

1|Updated Sep 6, 2015

Search Tags:#debugging #git history #anomaly detection #forensics #incident report #planning artifacts #workflow diagnosis

Ready to run

npx skills add https://github.com/deerawan/dotfiles --skill gsd-forensics-deerawan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-forensics
Source: https://github.com/deerawan/dotfiles/tree/main/claude/skills/gsd-forensics
Command: npx skills add https://github.com/deerawan/dotfiles --skill gsd-forensics-deerawan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you perform a post-mortem investigation of failed or stuck GSD workflows so you can identify what actually went wrong and what to do next.

Core Features & Use Cases

Evidence-based workflow diagnosis: Analyzes git history, repository state, and .planning/ artifacts to ground conclusions in concrete data.
Anomaly detection across common failure modes: Checks for patterns like stuck loops, missing artifacts, abandoned work, and crash/interruption signals.
Actionable forensics output: Produces a structured report saved under .planning/forensics/ and presents findings inline, with optional issue creation when appropriate.

Quick Start

Use the gsd-forensics skill to investigate a failed run by providing a brief problem description, so it generates a timestamped forensic report in .planning/forensics/.

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 workflow execution using git history and planning artifacts?▼

To diagnose a failed workflow execution, you can run a forensic analysis that correlates git history, repository state, and `.planning/` artifacts to identify likely anomalies and generate a structured incident report.

What is workflow forensics for post-mortem analysis of stuck development loops?▼

Workflow forensics for post-mortem analysis is the process of examining git history, session tracking files, and phase-level plans to detect anomalies like stuck loops, missing artifacts, or abandoned work after an interruption.

Can I analyze missing planning artifacts and abandoned work from a crashed development session?▼

Yes, you can analyze missing planning artifacts and abandoned work by checking repository state and session tracking files for crash or interruption signals, which helps identify what went wrong during the execution.

How do I generate a structured incident report grounded in git history evidence?▼

You generate a structured incident report by performing a forensic diagnosis that examines specific evidence across commits and `.planning/` summaries, applying redaction requirements before writing the results to `.planning/forensics/`.

What's the best way to investigate stuck GSD workflows spread across commits and session tracking files?▼

The best way to investigate stuck GSD workflows is to cross-reference git history with phase-level plans and session tracking files, allowing you to pinpoint workflow failures and produce actionable forensic findings.

Do I need existing `.planning/` artifacts to perform a workflow diagnosis?▼

Yes, existing `.planning/` artifacts such as phase-level plans, summaries, and session tracking files are required as evidence sources to correlate repository state with git history for accurate anomaly detection.