gsd-health

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnosing planning directory health and repairing issues across repositories can be error-prone and time-consuming; this Skill automates the process by validating structure and applying guided fixes.

Core Features & Use Cases

  • Validate directory structure and presence of required files in the .planning folder.
  • Detect misconfigurations and orphaned plans, and optionally initiate repairs.
  • Apply repair workflows via the health.md workflow when requested to restore consistent state.

Quick Start

Run the health workflow on your repository to diagnose the .planning directory and repair issues 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 planning directory structure and detect orphaned plans in a repository?

Validating planning directory structure involves checking the .planning folder for required files, verifying config consistency, and detecting orphaned plans across maintenance workflows to report actionable findings.

What is the best way to repair planning directory health issues automatically?

Repairing planning directory health issues is done by triggering the repair workflow with a --repair flag, which applies guided fixes via the health.md workflow to restore a consistent repository state.

Does this planning directory validation require a specific folder setup in my repository?

Planning directory validation requires a .planning folder in your repository, as the health workflow validates file presence and config consistency specifically within that directory structure.

Why does my planning directory health check report misconfigurations and missing files?

Planning directory health checks report misconfigurations and missing files when required files in the .planning folder are absent or config consistency rules are violated across maintenance workflows.

Can I automate planning directory health diagnosis across multiple maintenance workflows?

Automating planning directory health diagnosis works by validating file presence and detecting orphaned plans across maintenance workflows, reducing manual error-prone checks in repository management.