gsd-health

To check planning directory integrity, run a diagnostic validation against your `.planning/` workspace to identify missing files, invalid configurations, inconsistent state, and orphaned plans. This process returns an actionable report detailing any detected issues without modifying the directory.

Orphaned plans and broken configurations in a planning workspace silently degrade over time, causing misaligned state and missing artifacts. Diagnosing these integrity issues returns a detailed report so you can understand exactly what requires attention before attempting automated fixes.

To automatically repair misconfigured state and orphaned plans, execute the diagnostic tool with the `--repair` flag. After validating the `.planning/` directory state, the tool attempts to repair detected integrity issues automatically rather than just reporting them.

Yes, you can evaluate running-session context utilization by passing the `--context` flag. This queries validation mappings to classify context utilization as healthy, warning, or critical, recommending next steps if reasoning quality trends toward critical limits.

Yes, the planning directory repair workflow operates without external dependencies. It parses `--repair` and `--context` flags internally to validate state, execute repairs, and query context validation mappings directly against the `.planning/` workspace structure.

You should avoid using automated repair on a planning directory when you need to audit issues manually first. Run the default validation without the `--repair` flag to generate a diagnostic report of missing files and orphaned plans before allowing automated modifications.