qsd-next

Detect and advance qsd project state to the next workflow step.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect and automatically advance the current qsd project state to the next workflow step.

Core Features & Use Cases

  • Auto-detects the current phase by inspecting STATE.md, ROADMAP.md, and phase directories.
  • Invokes the next logical qsd workflow step without requiring user input.
  • Respects safety gates, with an optional --force flag to bypass checks when necessary.

Quick Start

Run the next-qsd workflow to advance to the subsequent phase based on the current state.

Frequently Asked Questions about qsd-next

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

FAQPage Schema
How do I automate advancing my project to the next workflow step?

To automate project workflow step transitions, this Skill reads local state files like STATE.md and ROADMAP.md to detect the current phase and invokes the next logical action defined in workflows/next.md without requiring manual input.

How does automatic phase detection work for multi-project setups?

Automatic phase detection works by inspecting local STATE.md, ROADMAP.md, and phase directories within your multi-project qsd setup to determine the current state and identify the exact next workflow step to execute.

Can I bypass safety gates when transitioning project phases automatically?

Yes, you can bypass safety gates during project phase transitions by using the optional --force flag, which overrides standard checks to force the workflow advancement when necessary.

What do I need to set up before running automated workflow state transitions?

You need local qsd state files initialized, specifically STATE.md, ROADMAP.md, and phase directories, along with the workflows/next.md definition file to orchestrate deterministic step transitions.

Why is my automated workflow phase transition not advancing correctly?

Automated workflow phase transitions rely on accurate local state files; if STATE.md, ROADMAP.md, or phase directories are missing or misconfigured, the state detection logic cannot determine the correct next action.