gsd-next

Detect and initiate the next logical step in multi-project GSD workflows from STATE.md and ROADMAP.md files.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/onelee85/my-skills --skill gsd-next
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-next
Source: https://github.com/onelee85/my-skills/tree/main/gsd-next
Command: npx skills add https://github.com/onelee85/my-skills --skill gsd-next

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates detection and initiation of the next logical step in multi-project GSD workflows, reducing the cognitive load of tracking phase progression across projects.

Core Features & Use Cases

  • Phase-driven progression: reads STATE.md, ROADMAP.md, and per-phase directories to decide the next action.
  • Deterministic execution: invokes the next GSD workflow end-to-end with minimal user input.
  • Multi-project readiness: scales across multiple concurrent projects without manual re-baselining.

Quick Start

Invoke gsd-next to determine and execute the next logical GSD workflow step based on STATE.md, ROADMAP.md, and phase folders.

Frequently Asked Questions about gsd-next

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

FAQPage Schema
How do I automate multi-project workflow state tracking to find the next phase?

Multi-project workflow state tracking is automated by reading STATE.md, ROADMAP.md, and phase directories to deterministically detect and invoke the next logical GSD workflow step. This reduces the cognitive load of manually tracking phase progression across concurrent projects.

What is the best way to advance project management phases deterministically without manual input?

Advancing project management phases deterministically relies on reading state files and roadmap configurations to orchestrate the next action. It invokes the subsequent workflow step end-to-end, ensuring execution proceeds with minimal user input required.

Does automated phase detection work with existing ROADMAP.md and STATE.md files?

Automated phase detection works directly with existing STATE.md, ROADMAP.md, and per-phase directories. It reads these files to decide the next action, requiring no additional dependencies or manual re-baselining to scale across multiple concurrent projects.

Can I use this workflow orchestration for rapid multi-project contexts?

Workflow orchestration is designed specifically for rapid multi-project contexts where tracking current phases is overhead. It scales across multiple concurrent projects by applying deterministic step selection to advance actions under a defined context using Cursor tools.

Why does deterministic step selection matter for GSD workflow automation?

Deterministic step selection matters because it ensures the GSD workflow advances to the exact next logical step without ambiguity. By reading phase directories and state files, it eliminates manual tracking errors and guarantees consistent end-to-end execution.

Do I need any external dependencies to run gsd-next for workflow orchestration?

No external dependencies are required to run workflow orchestration. It operates independently by parsing internal state and roadmap files to initiate the next logical phase, relying solely on the defined Cursor tool context for execution.