skills.rest
tinner-deinno
tinner-deinnoCOMMUNITY
Explore all skills by this author →
GitHub

gsd-forensics

Diagnose failed GSD workflows by reconstructing execution history from git logs and .planning artifacts.

1|Updated May 24, 2026
Search Tags:#git history#anomaly detection#forensics#workflow debugging#gsd#incident report#planning artifacts
One-click install
npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-forensics-tinner-deinno
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-forensics
Source: https://github.com/tinner-deinno/innova-skills-lib/tree/main/core/gsd/gsd-forensics
Command: npx skills add https://github.com/tinner-deinno/innova-skills-lib --skill gsd-forensics-tinner-deinno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you understand why a GSD workflow failed, got stuck, or produced the wrong outcome by reconstructing what happened from repository state and workflow artifacts.

Core Features & Use Cases

  • Workflow post-mortem diagnosis: correlates git history with workflow execution artifacts to identify where progress broke.
  • Evidence-based anomaly detection: checks for issues like stuck loops, missing planning artifacts, abandoned work, and crash/interruption patterns.
  • Actionable forensic output: writes a structured diagnostic report to .planning/forensics/ and offers recommendations and follow-up actions.

Quick Start

Run gsd-forensics and describe the problem you observed (for example, what you expected to happen and what actually happened), so the skill can generate an evidence-backed 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 stuck or interrupted multi-phase workflow?▼

Diagnose stuck workflows by reconstructing execution history from git logs and .planning artifacts. This process correlates repository state with workflow data to identify where progress broke, generating an evidence-grounded forensic report.

Why does my GSD workflow have missing planning artifacts and unexpected interruptions?▼

Missing planning artifacts and unexpected interruptions occur when execution anomalies disrupt multi-phase workflows. Evidence-based anomaly detection checks git history and workflow directories for crash patterns, stuck loops, and abandoned work to pinpoint the root cause.

Can I investigate incomplete workflow runs without modifying the repository state?▼

Investigate incomplete workflow runs safely using read-only investigation and session tracking. The forensic analysis extracts evidence strictly from existing git logs and .planning artifacts without altering the original repository state.

What's the best way to generate an incident report for failed workflow post-mortem analysis?▼

Generate an incident report for failed workflows by running a forensic diagnosis that correlates git history with execution artifacts. The structured diagnostic report is written directly to .planning/forensics/ with actionable recommendations.

Does this forensic diagnosis work with multi-phase workflow directories?▼

Forensic diagnosis works with multi-phase workflow directories by detecting anomalous progress across all phases. It reconstructs the timeline from git logs and .planning artifacts to identify missing phases or abandoned work.

What limitations exist when reconstructing workflow execution history from git logs?▼

Reconstructing workflow execution history from git logs is limited to evidence present in the repository and .planning artifacts. If workflow execution left no trace in git history or planning files, forensic diagnosis cannot identify the anomaly.

Related Skills

Explore More Software Engineering Skills→
hadpadrahulhadpadrahul

gsd-forensics

Diagnose failed GSD workflows by analyzing git history and planning artifacts.

Community
Advanced
jedmamostojedmamosto

gsd-forensics

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

Community
Advanced
rkz91rkz91
264

gsd-forensics

Analyze git history, planning artifacts, and session state to identify root causes of failed GSD workflows.

Community
Advanced
FlintmereFlintmere

debug-prod-incident

Trace production incidents into evidence-backed timelines and root-cause hypotheses.

Official
Advanced