gsd-next

Detect the current GSD phase from STATE.md and execute the next workflow step.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-next-artriv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-next
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-next
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-next-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the friction of forgetting which phase and step you’re in within a GSD workflow, so you can keep progressing without manual tracking.

Core Features & Use Cases

  • Workflow state detection: Determines the current project state by reading STATE.md, ROADMAP.md, and phase directories.
  • Automated next-step execution: Invokes the next logical step end-to-end by running the workflow defined in @.github/get-shit-done/workflows/next.md.
  • Use case: In a multi-project setup, you can switch contexts frequently and still have your automation pick up exactly where you left off, moving you forward with minimal cognitive overhead.

Quick Start

Use the gsd-next skill to detect your current GSD phase from STATE.md and automatically execute the next workflow step from @.github/get-shit-done/workflows/next.md.

Frequently Asked Questions about gsd-next

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

FAQPage Schema
How does workflow automation detect the current project phase in a multi-project setup?

Workflow automation detects the current project phase by reading STATE.md, ROADMAP.md, and phase directories to resolve the project's state. This state detection mechanism identifies exactly where you left off across multiple projects.

How do I automatically execute the next step in a GSD workflow?

To automatically execute the next GSD workflow step, invoke the automation to read your current state files and run the workflow defined in the @.github/get-shit-done/workflows/next.md file end-to-end.

Can I use state detection to switch contexts frequently without manual tracking?

Yes, state detection allows you to switch contexts frequently in a multi-project setup without manual tracking. The automation reads your state files and picks up exactly where you left off with minimal cognitive overhead.

What's the best way to maintain roadmap progress across multiple automated projects?

The best way to maintain roadmap progress is using automated next-step execution that consults ROADMAP.md and STATE.md. This approach ensures your workflow advances logically without the friction of forgetting your current phase.

Do I need STATE.md and ROADMAP.md files to run automated next-step execution?

Yes, you need STATE.md and ROADMAP.md files along with phase directories to run automated next-step execution. These files are required inputs for the automation to detect your current project state and determine the next logical step.

Why does my workflow automation fail to advance to the next phase?

Workflow automation fails to advance when it cannot properly read STATE.md or ROADMAP.md, or when phase directories are missing. Accurate state detection depends entirely on these files being present and correctly formatted.