gsd-forensics

Analyze git history and planning artifacts to diagnose failed GSD workflows.

264|11|Updated Apr 25, 2026

Search Tags:#post-mortem #git history #anomaly detection #forensics #workflow debugging #planning artifacts

Ready to run

npx skills add https://github.com/coco-research/coco --skill gsd-forensics-coco-research

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill investigates why a GSD workflow failed, stalled, or drifted from plan so you can quickly identify the root cause and decide the next corrective action.

Core Features & Use Cases

Failure Analysis: Reviews git history, status, diffs, and planning artifacts to reconstruct what happened.
Anomaly Detection: Checks for stuck loops, missing artifacts, abandoned work, and crash or interruption patterns.
Evidence-Based Reporting: Produces a structured forensic report with findings, recommendations, and optional escalation paths.
Use Case: Use it after an incomplete automation run to understand whether the issue came from missing files, interrupted execution, or inconsistent state.

Quick Start

Ask the skill to investigate the failed GSD workflow and generate a forensic report from the planning artifacts and git history.

Frequently Asked Questions about gsd-forensics

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

FAQPage Schema

How do I debug a failed workflow and find the root cause in git history?▼

Workflow debugging identifies root causes of failed orchestration runs by analyzing git history, planning artifacts, and filesystem state to reconstruct events and detect anomalies. It reviews diffs and status to determine why execution stalled or crashed.

What is post-mortem forensics for incomplete automation runs?▼

Post-mortem forensics investigates stalled or crashed automation workflows by examining planning artifacts and git history for missing files or interrupted execution. It classifies anomalies and generates evidence-backed reports to guide corrective actions.

How do I detect anomalies like stuck loops or abandoned work in a stalled workflow?▼

Anomaly detection scans git history and filesystem state to identify stuck loops, missing artifacts, abandoned work, and crash patterns. It checks planning artifacts to classify workflow inconsistencies and interruption points for forensic reporting.

Can I generate a forensic report from planning artifacts after a crashed orchestration run?▼

Yes, you can generate a forensic report from planning artifacts after a crashed orchestration run. The analysis produces structured findings, recommendations, and optional escalation paths written as redacted output to the .planning/forensics/ directory.

Does workflow debugging require any dependencies to analyze filesystem state?▼

No dependencies are required to analyze filesystem state and git history for workflow debugging. The investigation relies on existing planning artifacts, git diffs, and filesystem metadata to reconstruct failed orchestration runs and classify anomalies.

What's the best way to investigate inconsistent state after an interrupted workflow?▼

The best way to investigate inconsistent state after an interrupted workflow is evidence-backed forensics that examines git history, planning artifacts, and filesystem conditions. This approach distinguishes missing files from interrupted execution to identify the root cause.