Every premium and members-only resource for $9.99/month, as a no-commitment subscription. See the plans

PalateKit

Menu

Request a resource

Describe the resource you are missing in one sentence. We will email you when it is published.

0 / 280

Unlock PalateKit

Unlock everything

Plan

Paying means accepting our terms of sale.

Secure payment by Stripe. Receipts and invoices sent by email.

Welcome back

Sign in to install, download or save this resource. A free account is enough for free resources.

Investigating a failed GSD workflow v1.0.0

Use this resource to understand why a GSD workflow failed or got stuck

New

  • 359 downloads
  • 142 likes
  • 139 saves

Free

Install with the CLI

In a terminal, from the folder you want:

npx --yes palatekit@latest install diagnose-failed-workflow-runs

With no option, the skill goes to ~/.agents/skills/; add --agent claude-code (or codex, cursor…) to target an agent.

First time: connect the CLI with

npx --yes palatekit@latest login

The agent reviews the git history, the .planning/ files and the file system state, spots anomalies and writes a diagnostic report in .planning/forensics/. You can take a root cause and a corrective action from it, or open an issue.

Mostly picked by

Updated November 2, 2026

Card for the “Investigating a failed GSD workflow” skill

Details

Generates with
Your agent's model
Licence
MIT

Similar resources

View all

What you get

  • SKILL.md: sources reviewed (git history, artifacts, file state)
  • SKILL.md: diagnostic report and optional issue creation

Good fit for

  • A GSD run stopped without a clear reason
  • You want to understand where an inconsistent state came from

Not for

    Tags

    • diagnosis
    • investigation
    • history
    • workflow

    About

    You say

    “Investigate why the phase 2 run stopped.”

    Card for the “Investigating a failed GSD workflow” skill

    Skill published by davepoon under the MIT license, delivered in its original version.

    Show more

    How to use it

    1. Install the skill in your agent's skills folder
    2. Ask your agent to understand why a GSD workflow failed or got stuck
    3. Review and adjust the result

    Content preview

    Files

    • LICENSE1 KB
    • NOTICE-PALATEKIT.md0.5 KB
    • SKILL.md2.4 KB

    Origin and licence

    Listed unmodified

    Author
    davepoon
    Source
    github.com/davepoon/buildwithclaude/tree/75c22add059d710b269153142600ec8ef21c2092/plugins/gsd/skills/forensics
    Licence
    MIT

    Notice

    « gsd:forensics » (davepoon, MIT) livré dans sa version d'origine : fiche en français et en anglais par PalateKit.

    User reviews

    –

    No ratings yet

    Loading reviews…

    Delete your review?

    Your rating and comment will be removed from the page.