skills.rest
electroheadfx
electroheadfxCOMMUNITY
Explore all skills by this author →
GitHub

gsd-forensics

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

4|Updated Apr 11, 2026
Search Tags:#debugging#post-mortem#workflow analysis#git history#forensics#planning artifacts
One-click install
npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-forensics-electroheadfx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gsd-forensics
Source: https://github.com/electroheadfx/efx-mux/tree/main/.codex/skills/gsd-forensics
Command: npx skills add https://github.com/electroheadfx/efx-mux --skill gsd-forensics-electroheadfx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill investigates failed, stalled, or incomplete GSD workflows so you can understand why progress stopped and what evidence supports that conclusion.

Core Features & Use Cases

  • Workflow Post-Mortem: Reviews git history, uncommitted changes, and planning artifacts to find where execution diverged.
  • Anomaly Detection: Checks for stuck loops, missing artifacts, abandoned work, and crash or interruption patterns.
  • Evidence-Based Reporting: Produces a structured forensic report grounded in repository state, with recommendations and optional next steps.
  • Use Case: Use this Skill after a GSD session fails to finish a plan, leaves partial artifacts, or appears to be looping without progress.

Quick Start

Ask the gsd-forensics skill to investigate the most recent failed workflow and summarize the root cause with evidence.

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

To diagnose a stalled workflow, you investigate git history, workspace state, and planning artifacts to find where execution diverged. This evidence-based post-mortem identifies why progress stopped and what repository anomalies caused the interruption.

What causes incomplete workflows to leave missing deliverables in a repository?▼

Incomplete workflows leave missing deliverables due to execution divergence, stuck loops, or crash and interruption patterns. Analyzing uncommitted changes and phase files reveals these anomalies and grounds the forensic findings.

How do I perform a post-mortem analysis on abandoned plans and interrupted sessions?▼

Performing a post-mortem on abandoned plans requires gathering evidence from commits, diffs, and session records. This process detects inconsistent progress and produces a structured forensic report explaining the failure.

When should I run a forensic analysis on inconsistent progress in my repository?▼

Run a forensic analysis on inconsistent progress when a session fails to finish a plan, leaves partial artifacts, or appears to be looping without progress. This identifies stuck loops and missing artifacts.

Can I generate a forensic report with recommendations from uncommitted changes and diffs?▼

Yes, you can generate a forensic report grounded in repository state from uncommitted changes and diffs. The report includes root cause summaries, recommendations, and optional next steps based on the evidence.

Related Skills

Explore More Software Engineering Skills→
onelee85onelee85

gsd-forensics

Analyze git history and artifacts to document failed GSD workflow root causes.

Community
Advanced
D0NMEGAD0NMEGA
8

gsd-forensics

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

Community
Advanced
Poom5741Poom5741

gsd-forensics

Diagnose failed GSD workflows by analyzing git history, artifacts, and state.

Community
Advanced
yusaduymazyusaduymaz

gsd-forensics

Diagnose failed GSD workflow runs by tracing root causes in git history and artifacts.

Community
Advanced