gsd-forensics
From the author
Use when a GSD run failed, stalled, or produced the wrong result and the cause is unclear. Reads git history and .planning/ state and phase artifacts to diagnose root cause, then writes a report to .planning/forensics/.
Install
npx skills add coco-research/coco --skill gsd-forensics -a claude-code
Installs to .claude/skills/gsd-forensics/ · Each command fetches the skill straight from GitHub with the open skills CLI.
No download: this skill’s licence (Custom or unclear) does not let us redistribute its files. The install commands fetch them from GitHub instead.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 82
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- gsd-debugcoco-research/cocoUse when a bug, failing test, or unexpected behaviour needs investigation, especially across sessions or context resets. Isolates it in a debugger subagent with persistent .planning/debug state, unlike skills/systematic-debugging.Engineering★ 911
- gsd:progressdavepoon/buildwithclaudeCheck project progress, show context, and route to next action (execute or plan). Use --forensic to append a 6-check integrity audit after the standard report.Security★ 3.7K
- gsd-healthcoco-research/cocoUse when .planning/ looks inconsistent, files are missing, or state seems wrong. Validates .planning/ integrity, reports missing files, bad config, and orphaned plans, and --repair fixes what it finds.Planning★ 911
- gsd-statscoco-research/cocoUse when the user asks how big the project is, what has shipped, or for project statistics. Reports phase progress, plan execution, requirements completion, git history metrics, and timeline through the GSD workflow.Planning★ 911
- gsd-plan-phasecoco-research/cocoUse after a phase has been discussed, or when the user asks for a PLAN.md for a roadmap phase. Researches, spawns gsd-planner, verifies with gsd-plan-checker, and iterates; supports --gaps, --prd, --skip-research.Planning★ 911
- gsd-code-reviewcoco-research/cocoUse after a phase's code is written, or when the user asks to review changed files for bugs, security issues, or quality. Spawns the gsd-code-reviewer agent at quick, standard, or deep depth and writes the phase REVIEW.md.Engineering★ 911
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in