gsd-health

Validate your planning directory by running the health workflow end-to-end to detect missing files, invalid configurations, and inconsistent state. The process produces actionable reporting with clear next steps to fix your .planning/ hierarchy before downstream failures occur.

Planning workflow automation breaks due to missing planning files, invalid configuration, inconsistent workflow state, or orphaned plans within the .planning/ directory. Diagnosing directory health identifies these issues early so CI diagnostics can prevent downstream pipeline failures.

Yes, you can repair orphaned plans and configuration issues by invoking the health workflow with the --repair argument. This enables the tool to attempt automated fixes on detected problems while parsing and forwarding the flag correctly during the end-to-end run.

Troubleshoot planning configuration issues by running directory health validation to inspect the .planning/ hierarchy. This CI diagnostics process generates actionable failure reports, allowing you to address invalid configurations and inconsistent workflow state before integration breaks.

The best way to maintain directory health is running validation workflows that check the .planning/ hierarchy for missing files and inconsistent state. Applying the optional --repair argument during validation allows you to attempt remediation and keep workflow automation healthy.

Yes, planning directory validation works without external dependencies or components. The health workflow runs end-to-end independently to validate the .planning/ hierarchy, requiring only the optional --repair argument if you want to enable automated fix attempts for detected issues.