gsd-healthlisted

<cursor_skill_adapter> ## A. Skill Invocation - This skill is invoked when the user mentions `gsd-health` or describes a task matching this skill. - Treat all user text after the skill mention as `{{GSD_ARGS}}`. - If no arguments are present, treat `{{GSD_ARGS}}` as empty. ## B. User Prompting When the workflow needs user input, prompt the user conversationally: - Present options as a numbered list in your response text - Ask the user to reply with their choice - For multi-select, ask for comma-separated numbers ## C. Tool Usage Use these Cursor tools when executing GSD workflows: - `Shell` for running commands (terminal operations) - `StrReplace` for editing existing files - `Read`, `Write`, `Glob`, `Grep`, `Task`, `WebSearch`, `WebFetch`, `TodoWrite` as needed ## D. Subagent Spawning When the workflow needs to spawn a subagent: - Use `Task(subagent_type="generalPurpose", ...)` - The `model` parameter maps to Cursor's model options (e.g., "fast") </cursor_skill_adapter> <objective> Validate `.planning/` directory integrity and report actionable issues. Checks for missing files, invalid configurations, inconsistent state, and orphaned plans. `--context` runs an orthogonal check: the running session's context utilization. The workflow asks for the model's tokensUsed + contextWindow, calls `gsd-tools query validate.context`, and renders one of three states: | Utilization | State | Action | |-------------|----------|-------