name: gsd-next description: "Automatically advance to the next logical step in the GSD workflow" allowed-tools:
- Read
- Bash
- Grep
- Glob
- SlashCommand
<objective> Detect the current project state and automatically invoke the next logical GSD workflow step. No arguments needed — reads STATE.md, ROADMAP.md, and phase directories to determine what comes next.
Designed for rapid multi-project workflows where remembering which phase/step you're on is overhead. </objective>
<!-- Workflow content (was: next.md) --> <purpose> Detect current project state and automatically advance to the next logical GSD workflow step. Reads project state to determine: discuss → plan → execute → verify → complete progression. </purpose><required_reading> Read the skill content below before starting. </required_reading>
<process> <step name="detect_state"> Read project state to determine current position:# Get state snapshot
node "$GSD_TOOLS" state json 2>/dev/null || echo "{}"
Also read:
.planning/STATE.md— current phase, progress, plan counts.planning/ROADMAP.md— milestone structure and phase list
Extract:
current_phase— which phase is activeplan_of/plans_total— plan execution progressprogress— overall percentagestatus— active, paused, etc.
If no .planning/ directory exists:
No GSD project detected. Run `/gsd-new-project` to get started.
Exit. </step>
<step name="determine_next_action"> Apply routing rules based on state:Route 1: No phases exist yet → discuss
If ROADMAP has phases but no phase directories exist on disk:
→ Next action: /gsd-discuss-phase <first-phase>
Route 2: Phase exists but has no CONTEXT.md or RESEARCH.md → discuss
If the current phase directory exists but has neither CONTEXT.md nor RESEARCH.md:
→ Next action: /gsd-discuss-phase <current-phase>
Route 3: Phase has context but no plans → plan
If the current phase has CONTEXT.md (or RESEARCH.md) but no PLAN.md files:
→ Next action: /gsd-plan-phase <current-phase>
Route 4: Phase has plans but incomplete summaries → execute
If plans exist but not all have matching summaries:
→ Next action: /gsd-execute-phase <current-phase>
Route 5: All plans have summaries → verify and complete
If all plans in the current phase have summaries:
→ Next action: /gsd-verify-work
Route 6: Phase complete, next phase exists → advance
If the current phase is complete and the next phase exists in ROADMAP:
→ Next action: /gsd-discuss-phase <next-phase>
Route 7: All phases complete → complete milestone
If all phases are complete:
→ Next action: /gsd-complete-milestone
Route 8: Paused → resume
If STATE.md shows paused_at:
→ Next action: /gsd-resume-work
</step>
## GSD Next
**Current:** Phase [N] — [name] | [progress]%
**Status:** [status description]
▶ **Next step:** `/gsd-[command] [args]`
[One-line explanation of why this is the next step]
Then immediately invoke the determined command via SlashCommand.
Do not ask for confirmation — the whole point of /gsd-next is zero-friction advancement.
</step>
<success_criteria>
- Project state correctly detected
- Next action correctly determined from routing rules
- Command invoked immediately without user confirmation
- Clear status shown before invoking </success_criteria>