gsd-health

Name: gsd-health
Availability: InStock
Author: rkz91

Diagnose and repair .planning directory integrity issues with a --repair flag.

264|11|Updated Apr 25, 2026

Search Tags:#automation #workflow #validation #diagnose #health #repair #planning-directory

Ready to run

npx skills add https://github.com/rkz91/coco --skill gsd-health-rkz91

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-health
Source: https://github.com/rkz91/coco/tree/main/systems/gsd/skills/gsd-health
Command: npx skills add https://github.com/rkz91/coco --skill gsd-health-rkz91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose issues in the planning directory (.planning) and optionally repairs problems to restore healthy state.

Core Features & Use Cases

Validates the .planning/ directory integrity and surfaces actionable issues.
Detects missing files, invalid configurations, inconsistent state, and orphaned plans.
Use cases include ensuring planning environments are consistent across projects and ready for automated workflows.

Quick Start

Run the health workflow to scan your .planning directory and produce a repair report.

Frequently Asked Questions about gsd-health

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

FAQPage Schema

How do I validate a planning directory for missing files and inconsistent state?▼

You can validate a planning directory by running a health workflow that scans the .planning folder to detect missing files, invalid configurations, and inconsistent state, then surfaces actionable issues for resolution.

Can I automatically repair orphaned plans and invalid metadata in my project directory?▼

Yes, you can automatically repair orphaned plans and invalid metadata by running the health workflow with a --repair flag, which performs automated fixes to restore the planning directory to a healthy state.

What causes orphaned plans and inconsistent state across multiple project directories?▼

Orphaned plans and inconsistent state occur when planning directory structures drift across multiple projects due to missing files, invalid metadata, or broken configurations that diverge from the expected workflow standard.

Does the planning directory health check require any specific filesystem access or dependencies?▼

The health check requires local filesystem access and reads its workflow logic from a health.md file located in the get-shit-done workflows directory, but operates without external package dependencies.

What is the best way to ensure planning environments are consistent across multiple projects?▼

The best way to ensure consistency across multiple projects is to run a directory health diagnosis that validates .planning integrity, detects orphaned plans, and optionally applies automated repairs to align configurations.

Why is my automated workflow failing due to planning directory issues?▼

Automated workflows fail when the .planning directory contains missing files, invalid metadata, or inconsistent state, which breaks the expected directory structure and plan configurations required for processing.