gsd-health

Diagnose .planning directory health and repair issues via --repair flag.

8|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-health-d0nmega
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-health
Source: https://github.com/D0NMEGA/donnyclaude/tree/main/packages/skills/gsd-health
Command: npx skills add https://github.com/D0NMEGA/donnyclaude --skill gsd-health-d0nmega

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The health checker identifies gaps and misconfigurations in the .planning directory, helping teams prevent broken automation and stalled workflows.

Core Features & Use Cases

  • Validates the integrity of planning files and configurations and reports actionable issues.
  • Supports optional repair mode to fix common problems via the --repair flag.
  • Useful for project maintenance, automation workflows, and CI setups that rely on healthy planning data.

Quick Start

Run the gsd-health skill to validate your .planning directory and repair issues if needed.

Frequently Asked Questions about gsd-health

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

FAQPage Schema
How do I check the health of my .planning directory for missing files or misconfigurations?

To check planning directory health, run a validation workflow that scans .planning files for integrity issues. It identifies missing files, misconfigurations, and orphaned plans, then reports actionable findings to prevent stalled automation workflows.

Can I automatically repair orphaned plans and misconfigurations in my planning files?

Yes, you can repair orphaned plans and common misconfigurations by running the validation workflow with the --repair flag. This optional mode attempts to automatically fix detected issues, restoring planning data integrity for your project maintenance.

Why does my automation workflow stall when planning data is misconfigured?

Automation workflows stall when planning data is misconfigured because dependencies on healthy planning files break. Validating the .planning directory surfaces these gaps and orphaned plans, allowing you to repair issues and prevent broken project automation.

What is the best way to validate planning file integrity in a CI setup?

The best way to validate planning file integrity in CI setups is to run a validation workflow that checks the .planning directory. It reports actionable issues like missing files and supports an optional repair mode to fix problems automatically.

Do I need any dependencies to run a planning directory health check?

No external dependencies are required to run the planning directory health check. The validation workflow operates independently to scan .planning files, identify misconfigurations, and optionally repair issues using the --repair flag.

What types of issues can a .planning directory health check identify?

A .planning directory health check identifies missing files, misconfigurations, and orphaned plans. The validation workflow surfaces these actionable issues, helping teams maintain planning integrity and prevent broken automation in project maintenance scenarios.