gsd-health
Checks for structural integrity in planning directories and fixes common issues.
Install
mkdir -p .claude/skills/gsd-health && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/12852" && unzip -o skill.zip -d .claude/skills/gsd-health && rm skill.zipInstalls to .claude/skills/gsd-health
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Diagnose planning directory health and optionally repair issuesKey capabilities
- →Diagnose `.planning/` directory integrity
- →Check for missing GSD files
- →Identify invalid GSD configurations
- →Detect inconsistent GSD state
- →Find orphaned GSD plans
- →Optionally repair identified issues
How it works
The skill scans the `.planning/` directory for missing files, invalid configurations, inconsistent state, and orphaned plans, then reports these issues and can optionally repair them.
Inputs & outputs
When to use gsd-health
- →Check planning directory integrity
- →Fix broken GSD state
- →Verify project health
- →Repair missing artifacts
About this skill
<codex_skill_adapter>
A. Skill Invocation
- This skill is invoked by mentioning
$gsd-health. - Treat all user text after
$gsd-healthas{{GSD_ARGS}}. - If no arguments are present, treat
{{GSD_ARGS}}as empty.
B. AskUserQuestion → request_user_input Mapping
GSD workflows use AskUserQuestion (Claude Code syntax). Translate to Codex request_user_input:
Parameter mapping:
header→headerquestion→question- Options formatted as
"Label" — description→{label: "Label", description: "description"} - Generate
idfrom header: lowercase, replace spaces with underscores
Batched calls:
AskUserQuestion([q1, q2])→ singlerequest_user_inputwith multiple entries inquestions[]
Multi-select workaround:
- Codex has no
multiSelect. Use sequential single-selects, or present a numbered freeform list asking the user to enter comma-separated numbers.
Execute mode fallback:
- When
request_user_inputis rejected (Execute mode), present a plain-text numbered list and pick a reasonable default.
C. Task() → spawn_agent Mapping
GSD workflows use Task(...) (Claude Code syntax). Translate to Codex collaboration tools:
Direct mapping:
Task(subagent_type="X", prompt="Y")→spawn_agent(agent_type="X", message="Y")Task(model="...")→ omit (Codex uses per-role config, not inline model selection)fork_context: falseby default — GSD agents load their own context via<files_to_read>blocks
Parallel fan-out:
- Spawn multiple agents → collect agent IDs →
wait(ids)for all to complete
Result parsing:
- Look for structured markers in agent output:
CHECKPOINT,PLAN COMPLETE,SUMMARY, etc. close_agent(id)after collecting results from each agent </codex_skill_adapter>
<execution_context> @C:/Users/gusta/OneDrive/Documentos/gerenciador-de-quadras/.codex/get-shit-done/workflows/health.md </execution_context>
<process> Execute the health workflow from @C:/Users/gusta/OneDrive/Documentos/gerenciador-de-quadras/.codex/get-shit-done/workflows/health.md end-to-end. Parse --repair flag from arguments and pass to workflow. </process>When not to use it
- →When the user needs to execute GSD workflows
- →When the user needs to modify project content outside of GSD planning files
Limitations
- →The skill is specific to GSD planning directories
- →The skill focuses on directory integrity and state consistency
- →The skill's repairs are limited to GSD-related issues
How it compares
This skill provides an automated health check and repair mechanism for GSD planning directories, ensuring workflow continuity and data integrity, unlike manual inspection and correction.
Compared to similar skills
gsd-health side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| gsd-health (this skill) | 0 | 4mo | No flags | Beginner |
| dispatching-parallel-agents | 0 | 3mo | No flags | Advanced |
| n8n-expression-syntax | 6 | 4mo | No flags | Beginner |
| python-repl | 6 | 4mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by Gustavosareto
View all by Gustavosareto →You might also like
dispatching-parallel-agents
jorge-mendoza-corella
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
n8n-expression-syntax
czlonkowski
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, or working with webhook data in workflows.
python-repl
gptme
Interactive Python REPL automation with common helpers and best practices
n8n-validation-expert
czlonkowski
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, or the validation loop process.
powershell-windows
davila7
PowerShell Windows patterns. Critical pitfalls, operator syntax, error handling.
bats
OleksandrKucherenko
Bash Automated Testing System (BATS) for TDD-style testing of shell scripts. Use when: (1) Writing unit or integration tests for Bash scripts, (2) Testing CLI tools or shell functions, (3) Setting up test infrastructure with setup/teardown hooks, (4) Mocking external commands (curl, git, docker), (5) Generating JUnit reports for CI/CD, (6) Debugging test failures or flaky tests, (7) Implementing test-driven development for shell scripts.