gsd-health

Validate and repair inconsistencies in the .planning/ directory.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/onelee85/my-skills --skill gsd-health-onelee85
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-health
Source: https://github.com/onelee85/my-skills/tree/main/gsd-health
Command: npx skills add https://github.com/onelee85/my-skills --skill gsd-health-onelee85

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and repair inconsistencies in the .planning/ directory to ensure a healthy, predictable project workflow.

Core Features & Use Cases

  • Validate presence of required planning files and detect misconfigurations within a .planning/ directory.
  • Identify orphaned plans and inconsistent state across the planning workspace.
  • Offer automated repair options when a --repair flag is provided, and report concrete remediation steps.

Quick Start

Run the health workflow against your repository to validate and optionally repair the planning directory.

Frequently Asked Questions about gsd-health

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

FAQPage Schema
How do I validate missing files and misconfigurations in a planning directory?

To validate planning directory health, run a deterministic health workflow that parses the .planning/ directory to detect missing files, misconfigurations, and orphaned plans, reporting actionable remediation steps.

Can I automatically repair orphaned plans and inconsistent state in my project workspace?

Yes, you can automatically repair orphaned plans and inconsistent state by executing the health workflow with a --repair flag, which applies targeted fixes and reports concrete remediation steps.

What is directory health validation and when do I need it for project planning?

Directory health validation is the process of diagnosing inconsistencies in a .planning/ directory to ensure a predictable workflow, needed when orphaned plans or missing files disrupt project state.

Does the planning directory repair workflow require any external dependencies?

No, the planning directory repair workflow operates without external dependencies, running a deterministic health check directly against typical project setups within the planning domain.

What is the best way to diagnose inconsistent state across a planning workspace?

The best way to diagnose inconsistent state across a planning workspace is running a deterministic health workflow that identifies orphaned plans and misconfigurations, providing actionable remediation steps.

Why does my planning directory health check report misconfigurations and how do I fix them?

A planning directory health check reports misconfigurations when it detects invalid setups or missing files, which you fix by rerunning the workflow with the --repair flag to apply automated remediation.