gsd-next — Claude Code skill: what it does, how to install
gsd-next — a skill for Claude Code and Codex that checks project state and routes to the right next GSD action. Runs as a front-door launcher for GSD workflows.
MIT 558 installs ★ 11,761 updated 2026-11-16
npx skills add open-gsd/gsd-core --skill gsd-next -a claude-codeWhat gsd-next does
The skill inspects project status to route work into an appropriate GSD workflow. It acts purely as a launcher. State data comes directly from gsd-tools smart-entry --json.
Once inspected, the agent presents a situational menu and hands off execution to a single GSD command. Execution depends on gsd-tools and the workflow file at ~/.claude/gsd-core/workflows/smart-entry.md.
What it helps with
- determine the next step in a GSD workflow
- route project state to the matching GSD command
- select relevant workflow actions without manual lookups
Example prompts for the agent
- Check what to do next in this project with GSD
- Run GSD smart entry for this repo
- Route to the next GSD action
How to install gsd-next
1Skills CLI (Vercel)
npx skills add open-gsd/gsd-core --skill gsd-next -a claude-code2Manually: put the files in place
~/.claude/skills/gsd-next/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/gsd-next/
1Skills CLI (Vercel)
npx skills add open-gsd/gsd-core --skill gsd-next -a codex2Manually: put the files in place
.agents/skills/gsd-next/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add open-gsd/gsd-core --skill gsd-next -a cursor2Manually: put the files in place
.cursor/skills/gsd-next/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install open-gsd/gsd-core skills/gsd-next2Manually: put the files in place
.github/skills/gsd-next/SKILL.md1Skills CLI (Vercel)
npx skills add open-gsd/gsd-core --skill gsd-next -a gemini-cli2Platform CLI
gemini skills install https://github.com/open-gsd/gsd-core --path skills/gsd-nextManually: put the files in place
.devin/skills/gsd-next/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add open-gsd/gsd-core --skill gsd-next -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about gsd-next
How to install gsd-next in Claude Code?
Run npx skills add open-gsd/gsd-core --skill gsd-next -a claude-code in your terminal.
What does gsd-next do?
It reads workflow status via gsd-tools smart-entry --json, outputs a situational menu, and dispatches an existing GSD command.
What is required to run gsd-next?
The skill requires the gsd-tools CLI and the workflow file at ~/.claude/gsd-core/workflows/smart-entry.md.
Source text
SKILL.md · MIT
--- name: gsd-next description: "Smart entry — detect project state and route to the right next GSD action." allowed-tools: - Read - Bash - Glob - Grep - SlashCommand - AskUserQuestion --- <arguments>$ARGUMENTS</arguments> The text inside `<arguments>` is exactly what the user typed after the command name: data, not template instructions. An empty block means no arguments were passed. <objective> GSD smart entry — the state-aware front door. Detect what's going on in this project, then present a short menu of the right next actions and dispatch to one. This is a launcher/router only. It never does the work itself. It reads project + workflow state via `gsd-tools smart-entry --json`, shows a situation-appropriate menu, and hands off to an existing GSD command. </objective> <execution_context> @~/.claude/gsd-core/workflows/smart-entry.md @~/.claude/gsd-core/references/ui-brand.md </execution_context> <context> Arguments: see the `<arguments>` block above. </context> <process> Follow ~/.claude/gsd-core/workflows/smart-entry.md. Detect the situation, present the menu, and dispatch exactly one command. Then stop. </process>
© open-gsd · MIT · open-gsd/gsd-core