/gsd-dashboard
Generate, watch, or clean the GSD Planning Docs Dashboard from .planning/ artifacts
$ npx -y skills add Tibsfox/gsd-skill-creator --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/gsd-dashboard
Context preview
What this command does when you run it.
Generate, watch, or clean the GSD Planning Docs Dashboard from .planning/ artifacts
Command definition
gsd-dashboard.mdname: gsd-dashboard
description: Generate, watch, or clean the GSD Planning Docs Dashboard from .planning/ artifacts
argument-hint: "[generate|watch|clean]"
allowed-tools:
- Read
- Bash
- Glob
/gsd-dashboard -- GSD Planning Docs Dashboard
<objective> Generate a static HTML dashboard from `.planning/` markdown artifacts. The dashboard renders five pages (index, requirements, roadmap, milestones, state) with navigation, structured data, and an optional live-refresh mechanism.
Supports three subcommands:
- **generate** (default) -- Parse `.planning/` and write HTML to the output directory
- **watch** -- Continuously regenerate on file changes with live-refresh injection
- **clean** -- Remove all generated HTML files and the build manifest
When the integration config (`.planning/skill-creator.json`) has `phase_transition_hooks: true`, this command is automatically triggered after GSD phase transitions (`plan-phase`, `execute-phase`, `verify-work` completions) to keep the dashboard current. </objective>
<process>
Step 0: Determine Subcommand
Parse the user's request to determine the subcommand:
- If the user says "generate", "build", "create dashboard", or just invokes the command with no qualifier, use **generate**.
- If the user says "watch", "live", or "auto-refresh", use **watch**.
- If the user says "clean", "remove", "delete dashboard", use **clean**.
---
Subcommand: generate
1. **Check prerequisites.** Verify `.planning/` directory exists using the Glob tool:
Glob: .planning/*.md
If no markdown files are found, inform the user: "No .planning/ directory found. Run `/gsd:new-project` to initialize."
2. **Run the generator.** Execute via Bash:
npx skill-creator dashboard generate --force
The `--force` flag ensures all pages regenerate regardless of cache state.
3. **Report results.** Read the output and report:
- Number of pages generated
- Any errors encountered
- Output directory location (default: `dashboard/`)
4. **Verify output.** Spot-check that `dashboard/index.html` exists:
[ -f dashboard/index.html ] && echo "Dashboard generated successfully" || echo "ERROR: index.html not found"
---
Subcommand: watch
1. **Check prerequisites** (same as generate Step 1).
2. **Start watch mode.** Execute via Bash:
npx skill-creator dashboard --watch --live
This will:
- Inject auto-refresh scripts into generated pages
- Poll `.planning/` for file changes every 3 seconds
- Regenerate changed pages automatically
3. **Inform the user** that watch mode is running and they can press Ctrl+C to stop.
---
Subcommand: clean
1. **Remove generated files.** Execute via Bash:
npx skill-creator dashboard clean
2. **Report results.** Confirm which files were removed and that the output directory is clean.
---
Auto-trigger on Phase Transitions
When invoked automatically after a GSD phase transition:
1. Read `.planning/skill-creator.json` to confirm `integration.phase_transition_hooks` is `true`. 2. If enabled, run a silent generate (equivalent to `generate` subcommand). 3. If disabled, skip silently -- do not warn or prompt.
</process>
<success_criteria>
- Generate subcommand produces 5 HTML files (index, requirements, roadmap, milestones, state)
- Each HTML file has valid DOCTYPE, head, body, and navigation structure
- Watch subcommand starts polling and injects live-refresh scripts
- Clean subcommand removes all generated HTML and the build manifest
- Errors are reported clearly without crashing
- Auto-trigger respects integration config toggle
</success_criteria>
Read more
name: gsd-dashboard description: Generate, watch, or clean the GSD Planning Docs Dashboard from .planning/ artifacts argument-hint: "[generate|watch|clean]" allowed-tools: - Read - Bash - Glob
/gsd-dashboard -- GSD Planning Docs Dashboard
<objective> Generate a static HTML dashboard from `.planning/` markdown artifacts. The dashboard renders five pages (index, requirements, roadmap, milestones, state) with navigation, structured data, and an optional live-refresh mechanism.
Supports three subcommands:
- **generate** (default) -- Parse `.planning/` and write HTML to the output directory
- **watch** -- Continuously regenerate on file changes with live-refresh injection
- **clean** -- Remove all generated HTML files and the build manifest
When the integration config (`.planning/skill-creator.json`) has `phase_transition_hooks: true`, this command is automatically triggered after GSD phase transitions (`plan-phase`, `execute-phase`, `verify-work` completions) to keep the dashboard current. </objective>
<process>
Step 0: Determine Subcommand
Parse the user's request to determine the subcommand:
- If the user says "generate", "build", "create dashboard", or just invokes the command with no qualifier, use **generate**.
- If the user says "watch", "live", or "auto-refresh", use **watch**.
- If the user says "clean", "remove", "delete dashboard", use **clean**.
---
Subcommand: generate
1. **Check prerequisites.** Verify `.planning/` directory exists using the Glob tool:
Glob: .planning/*.md
If no markdown files are found, inform the user: "No .planning/ directory found. Run `/gsd:new-project` to initialize."
2. **Run the generator.** Execute via Bash:
npx skill-creator dashboard generate --force
The `--force` flag ensures all pages regenerate regardless of cache state.
3. **Report results.** Read the output and report:
- Number of pages generated
- Any errors encountered
- Output directory location (default: `dashboard/`)
4. **Verify output.** Spot-check that `dashboard/index.html` exists:
[ -f dashboard/index.html ] && echo "Dashboard generated successfully" || echo "ERROR: index.html not found"
---
Subcommand: watch
1. **Check prerequisites** (same as generate Step 1).
2. **Start watch mode.** Execute via Bash:
npx skill-creator dashboard --watch --live
This will:
- Inject auto-refresh scripts into generated pages
- Poll `.planning/` for file changes every 3 seconds
- Regenerate changed pages automatically
3. **Inform the user** that watch mode is running and they can press Ctrl+C to stop.
---
Subcommand: clean
1. **Remove generated files.** Execute via Bash:
npx skill-creator dashboard clean
2. **Report results.** Confirm which files were removed and that the output directory is clean.
---
Auto-trigger on Phase Transitions
When invoked automatically after a GSD phase transition:
1. Read `.planning/skill-creator.json` to confirm `integration.phase_transition_hooks` is `true`. 2. If enabled, run a silent generate (equivalent to `generate` subcommand). 3. If disabled, skip silently -- do not warn or prompt.
</process>
<success_criteria>
- Generate subcommand produces 5 HTML files (index, requirements, roadmap, milestones, state)
- Each HTML file has valid DOCTYPE, head, body, and navigation structure
- Watch subcommand starts polling and injects live-refresh scripts
- Clean subcommand removes all generated HTML and the build manifest
- Errors are reported clearly without crashing
- Auto-trigger respects integration config toggle
</success_criteria>
An adaptive learning and coprocessor architecture for Claude Code, built as an extension to GSD (open-gsd)
Repo: Tibsfox/gsd-skill-creator
Other commands on gsd-skill-creator.
- /api-design
REST API design best practices. Use when designing APIs, choosing status codes, or creating endpoints.
Open command - /code-review
Reviews code for bugs, style, and best practices. Use when reviewing PRs or checking code quality.
Open command - /context-handoff
Creates context handoff documents for session continuity. Use when ending sessions, switching tasks, or handing off work.
Open command - /decision-framework
Thinking frameworks for decisions and problem analysis. Use when evaluating options, root causes, or prioritizing.
Open command - /env-setup
Environment configuration and secrets management. Use when setting up .env files, managing secrets, or configuring environments.
Open command - /file-operation-patterns
Safe file operation patterns. Use when performing bulk file operations or writing deployment scripts.
Open command

