skills.rest
gyuha
gyuhaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

sg-next

Determine the current orchestration stage and route to the next sg-* command from STATE.md and HANDOFF.md files.

2|Updated May 15, 2026
Search Tags:#CLI automation#workflow orchestration#command routing#retrospection#stage detection#GSD#handoff logging
One-click install
npx skills add https://github.com/gyuha/super-gsd --skill sg-next
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sg-next
Source: https://github.com/gyuha/super-gsd/tree/main/.agents/skills/sg-next
Command: npx skills add https://github.com/gyuha/super-gsd --skill sg-next

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the fragile manual handoff between planning, implementation, and retrospection so you don’t lose workflow continuity or run the wrong next command.

Core Features & Use Cases

  • Stage detection from workflow logs: Reads .planning/STATE.md and .planning/HANDOFF.md to resolve the current stage.
  • Deterministic routing to the next skill: Maps the detected stage to the appropriate sg-* command (or sg-plan {phase} / sg-complete when applicable).
  • Audit-friendly handoff logging: Appends a HANDOFF.md row (From → sg-next) before reporting the next action, with safe numbered-choice handling for init and complete.

Quick Start

Run /super-gsd:sg-next whenever you want the plugin to detect your current stage and tell you exactly which /super-gsd:sg-* command to run next.

Frequently Asked Questions about sg-next

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically route to the next command in a CLI workflow orchestration loop?▼

Workflow orchestration routing detects your current stage by parsing workflow state files, validating stage enums, and emitting a single-line next-step instruction to execute the correct command.

How does stage detection infer phase transitions from handoff logs?▼

Stage detection infers phase transitions by reading .planning/STATE.md and .planning/HANDOFF.md, resolving the current orchestration stage, and appending an audit row before reporting the next action.

Can I automate command routing for init and complete stages without manual selection?▼

Command routing for init and complete stages requires safe numbered-choice handling, presenting numbered user choices to resolve ambiguous state transitions before routing to the next command.

What's the best way to maintain workflow continuity across planning, implementation, and retrospection?▼

Maintaining workflow continuity requires deterministic routing across the full GSD loop, using state and handoff files to map detected stages to appropriate commands and prevent manual handoff fragility.

Why does automated command routing fail when the workflow state file is missing?▼

Automated command routing fails without .planning/STATE.md because stage detection relies on parsing this file to validate current phase enums and infer the correct stage transition.

Related Skills

Explore More Software Engineering Skills→
gyuhagyuha
2

sg-start

Detect super-gsd workflow sessions and route to the next action.

Community
Intermediate
gyuhagyuha
2

sg-status

Read planning files and output the next super-gsd command.

Community
Intermediate
gyuhagyuha
2

sg-learn

Delegate structured retrospective execution to sg-retro for a specified phase.

Community
Basic
rbtkhnrbtkhn

handoff-check

Review active development handoff state and summarize re-entry context.

Community
Intermediate