gsd-next

Detect project state from STATE.md and ROADMAP.md and invoke the next workflow step.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-next-dobrinz123
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-next
Source: https://github.com/dobrinz123/claude-skills-share/tree/main/skills/gsd-next
Command: npx skills add https://github.com/dobrinz123/claude-skills-share --skill gsd-next-dobrinz123

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually determining the current project phase and deciding the next action across multiple projects is time-consuming and error-prone; gsd-next removes that overhead by detecting state and making the transition automatically.

Core Features & Use Cases

  • State Detection: Reads STATE.md, ROADMAP.md, and phase directories to determine the project's current position.
  • Automated Progression: Invokes the next logical GSD workflow end-to-end using the configured execution context.
  • Use Case: Ideal for teams running many parallel projects or milestones where an assistant must routinely choose and execute the next phase without manual orchestration.

Quick Start

Run the gsd-next skill to detect project state from STATE.md and ROADMAP.md and automatically advance to the next workflow step.

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 project workflow phases across multiple repositories?

Automated project workflow advancement detects the current state from STATE.md and ROADMAP.md files, then invokes the next logical workflow step to transition phases without manual orchestration across multiple projects.

What is state detection for project workflow transitions?

State detection for workflow transitions reads repository state files like STATE.md and ROADMAP.md alongside phase directories to determine a project's current position and decide the next action to execute automatically.

How do I manage phase transitions in multi-project development scenarios?

Multi-project phase transitions are managed by reading STATE.md and ROADMAP.md to identify the current phase, then executing predefined workflow instructions to advance each project to its next logical step without manual intervention.

Do I need specific state files to automate my project workflow progression?

Automated workflow progression requires STATE.md and ROADMAP.md files in the repository, plus configured workflow instructions stored in the ~/.claude/get-shit-done/workflows/next.md path for execution.

Can I use automated workflow progression for planning, execution, and handoff phases?

Automated workflow progression applies to planning, execution, and handoff phases by reading repository state files to determine the current position and invoking the appropriate predefined workflow for each phase transition.

What are the limitations of automated state detection for project workflows?

Automated state detection requires read access to repository state files and the ability to execute file and shell operations from predefined workflow paths, making it dependent on consistent STATE.md and ROADMAP.md file maintenance.