gsd-next

Auto-advancing the next workflow step works by reading STATE.md and ROADMAP.md to detect the current project phase and invoking the corresponding workflow end-to-end. This reduces cognitive overhead and manual tracking across multi-project environments.

Managing phase-based workflows across multiple projects is handled by reading local state files and predefined workflows to auto-detect phase directories. The skill determines upcoming phases from STATE.md and ROADMAP.md, enabling rapid multi-project handoffs without manual arguments.

No arguments are needed to advance your workflow phase. The skill automatically detects the current phase from local STATE.md and ROADMAP.md files, then executes the corresponding workflow end-to-end without manual input.

Yes, you can use local state files to trigger the next phase in an automated workflow. The skill reads STATE.md and ROADMAP.md to determine the upcoming phase and automatically invokes the next workflow step based on that local state data.

Multi-project workflows require manual tracking between phases when current state and roadmap data are not automatically parsed. This skill solves that by reading STATE.md and ROADMAP.md to detect the current phase and auto-advance to the next logical workflow step.

You should not rely on automated workflow progression when your project lacks valid STATE.md or ROADMAP.md files, as the skill depends on these local state files to detect the current phase and map to the next step for end-to-end execution.