Validate GSD, Superpowers, and hook installation and registration with OK/WARN/FAIL reports.
npx skills add https://github.com/gyuha/super-gsd --skill sg-health
Please help me install this Agent Skill. Skill: sg-health Source: https://github.com/gyuha/super-gsd/tree/main/skills/sg-health Command: npx skills add https://github.com/gyuha/super-gsd --skill sg-health
Use this Skill to quickly identify what’s missing or misconfigured when the GSD → Superpowers → sg-retro loop feels broken, especially during onboarding.
Run sg-health when something feels broken or before onboarding to get line-by-line OK/WARN/FAIL diagnostics for GSD, Superpowers, hooks, HANDOFF.md, and STATE.md without modifying any files.
High-intent search queries and answers about installing and using this skill.
Diagnose broken hook registration and stage handoffs by running a read-only validation command that checks ~/.claude/*, hooks.json, .planning/HANDOFF.md, and .planning/STATE.md. It reports each configuration item as OK, WARN, or FAIL with a final summary to quickly identify missing or misconfigured files.
Your GSD automation loop stops advancing when required Stop and SubagentStop hooks are not registered inside hooks.json, or when .planning/STATE.md frontmatter is malformed. A read-only diagnostic check validates these integrations and reports failures without modifying any files.
The best way to validate GSD and Superpowers installation during onboarding is to run a diagnostic check that verifies directory structures, Superpowers presence, and required hook scripts. It outputs a line-by-line OK, WARN, or FAIL status for each component to confirm the environment is wired correctly.
Check HANDOFF.md and STATE.md validity by running a diagnostic command that verifies the presence and content of .planning/HANDOFF.md and parses the frontmatter of .planning/STATE.md. This ensures stage tracking and handoffs will not silently fail due to missing or malformed files.
Yes, you can troubleshoot Superpowers orchestration without modifying files by running a read-only diagnostic command. It validates GSD installation, hook scripts, hooks.json registration, and planning files, then reports a FAIL or WARN summary without writing any changes to your system.
A WARN status during GSD and hook installation checks indicates a non-critical misconfiguration, such as the optional Hookify presence being missing. It distinguishes partial setups from critical FAIL errors like missing required hook scripts or unregistered Stop and SubagentStop hooks in hooks.json.
mattmacleod16-svgDevelop and enforce event-driven Claude Code hooks for tool automation.
gyuhaDetect super-gsd workflow sessions and route to the next action.
gyuhaDelegate structured retrospective execution to sg-retro for a specified phase.
cowwocValidate stakeholder requirement reports and agent statuses before synthesis.
