gsd-health

Diagnose and repair issues in the .planning directory with --repair flag.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose planning directory health and repair issues by validating structure, configurations, and plan consistency.

Core Features & Use Cases

  • Validate missing files, misconfigurations, and orphaned plans within the .planning/ directory.
  • Detect orphaned plans and ensure cross-plan consistency across the workflow.
  • Provide remediation guidance or automated repairs when the --repair flag is used.

Quick Start

Run the health workflow to scan and repair issues in your planning directory when requested.

Frequently Asked Questions about gsd-health

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

FAQPage Schema
How do I validate my project planning directory for missing files and misconfigurations?

To validate a planning directory, run a health workflow that scans the .planning configurations, checks for missing files, and detects orphaned plans to ensure project workflow consistency.

What is planning directory health repair and when do I need it?

Planning directory health repair is the process of diagnosing structural and consistency issues within .planning configurations. You need it when project workflows fail due to missing files, misconfigurations, or orphaned plans.

How do I run an automated repair on misconfigured planning files?

You can run an automated repair on misconfigured planning files by executing the health workflow and applying the --repair flag, which triggers automated fixes for detected directory inconsistencies.

How do I detect and resolve orphaned plans in my project workflow?

To detect and resolve orphaned plans, execute a plan consistency check across the planning directory. The health workflow identifies orphaned plans and provides remediation guidance or applies fixes with the --repair flag.

Does this planning directory validation require any external dependencies?

No, this planning directory validation requires no external dependencies. It operates directly on the .planning directory structure to read and execute health workflow definitions without additional tooling.

What is the best way to ensure cross-plan consistency across project workflows?

The best way to ensure cross-plan consistency is to run a health workflow that validates the .planning directory, checks configuration alignment, and detects orphaned plans across the entire project workflow.