gsd-next

Detect project state from STATE.md and ROADMAP.md to advance the GSD workflow.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/MINT-IA/MINT --skill gsd-next-mint-ia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-next
Source: https://github.com/MINT-IA/MINT/tree/main/.claude/skills/gsd-next
Command: npx skills add https://github.com/MINT-IA/MINT --skill gsd-next-mint-ia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically advance to the next logical step in the GSD workflow by detecting the current project state and triggering the appropriate next action without manual input.

Core Features & Use Cases

  • State detection: Reads STATE.md, ROADMAP.md, and phase directories to determine the next step.
  • Deterministic transitions: Executes the next workflow end-to-end with no arguments.
  • Multi-project support: Handles rapid transitions across multiple projects in parallel.

Quick Start

Run the skill to advance to the next GSD step based on the current project state.

Frequently Asked Questions about gsd-next

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

FAQPage Schema
How do I automatically advance to the next step in my project workflow?

To automatically advance your project workflow, you need a tool that detects the current state from local files and triggers the next action. This skill reads state files to execute deterministic transitions with no manual arguments required.

How does state detection work for multi-project roadmap management?

State detection for multi-project roadmap management works by reading local STATE.md, ROADMAP.md, and phase directories. It determines the correct next action for each project, enabling rapid parallel transitions across multiple environments.

Do I need to pass arguments to trigger the next project phase transition?

No, you do not need to pass arguments to trigger the next project phase transition. The skill operates with no arguments by reading local state files and workflow definitions to drive deterministic state transitions automatically.

Can I use this workflow state detection across multiple projects running in parallel?

Yes, you can use this workflow state detection across multiple projects running in parallel. It handles rapid transitions by reading individual project state files and roadmap definitions to determine the correct next action for each environment.

What is the best way to execute deterministic transitions in a GSD workflow?

The best way to execute deterministic transitions in a GSD workflow is to automate progression by reading local state files. This approach identifies the current project phase and invokes the next logical step end-to-end without manual intervention.

Why does my automated project workflow transition fail to detect the current state?

Automated project workflow state detection fails if local state files are missing or misconfigured. The skill relies on reading STATE.md, ROADMAP.md, and phase directories to determine the correct next action, so these files must exist and be accurate.