qsd-add-phase

Automate adding a new phase to the current milestone in a roadmap.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Roadmap planning often suffers from inconsistent phase numbering, missing phase directories, and out-of-sync STATE.md updates when adding a new phase to the end of the current milestone. This skill automates the process to ensure a clean, auditable expansion of milestones.

Core Features & Use Cases

  • Sequential phase creation: calculates the next phase number and creates the phase directory with a slug derived from the description.
  • Roadmap integrity: updates the roadmap and STATE.md to reflect changes across milestones.
  • Workflow-driven: leverages the add-phase workflow to handle validation, slug generation, and file mutations for end-to-end reliability.

Quick Start

Invoke the add-phase workflow to append a new phase with a short description to the current milestone.

Frequently Asked Questions about qsd-add-phase

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

FAQPage Schema
How do I add a new phase to a roadmap milestone without breaking file structure?

To append a roadmap phase, invoke the add-phase workflow with a short description. It handles argument parsing, milestone detection, next-phase calculation, and updates ROADMAP and STATE files end-to-end.

How does slug generation work when creating new phase directories?

Slug generation derives a URL-friendly directory name directly from the short phase description you provide, ensuring consistent naming conventions and clean file structure across roadmap milestones.

Why does my STATE.md file get out of sync when I manually add roadmap phases?

STATE.md updates fall out of sync during manual roadmap expansion due to inconsistent phase numbering and missing directories. Automating the add-phase workflow ensures auditable STATE.md updates and roadmap integrity.

Can I use this to append phases to any milestone in my roadmap?

This workflow appends a new phase specifically to the end of the current active milestone in your roadmap, calculating the next sequential phase number and creating the necessary directory structure.

What is the best way to maintain roadmap integrity across iterative planning cycles?

Maintaining roadmap integrity across iterative cycles requires consistent phase numbering, directory creation, and synchronized STATE.md updates, all handled automatically by the add-phase workflow during milestone expansion.