gsd-add-phase

Add the next sequential integer phase to a repository roadmap and update STATE.md.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-add-phase-artriv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gsd-add-phase
Source: https://github.com/ArtRiv/game-topicos-especiais/tree/main/.github/skills/gsd-add-phase
Command: npx skills add https://github.com/ArtRiv/game-topicos-especiais --skill gsd-add-phase-artriv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the manual effort of extending a roadmap by adding the next sequential milestone phase and keeping the repository state in sync.

Core Features & Use Cases

  • Next phase creation: Calculates the next integer phase number (ignoring decimals) and generates a slug from the provided phase description.
  • Roadmap evolution: Inserts the new phase entry into the roadmap structure for the current milestone.
  • State tracking: Updates STATE.md to record the roadmap evolution so the history stays consistent.

Use case: When your team completes a milestone and needs a new phase to start, you can supply a concise description and have the workflow create the correct directory and update both the roadmap and STATE.md automatically.

Quick Start

Request adding a new phase with a clear description of what the next phase should accomplish.

Frequently Asked Questions about gsd-add-phase

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

FAQPage Schema
How do I automatically add the next phase to a repository-driven roadmap?

To automate roadmap phase management, you provide a concise description of the next milestone phase. The system calculates the next sequential integer phase, generates a slug, creates the directory, and updates the roadmap structure and STATE.md simultaneously.

How does state tracking work when adding a new milestone phase?

State tracking works by updating STATE.md to record the roadmap evolution whenever a new phase is added. This ensures the repository history stays consistent and accurately reflects the current milestone phase structure.

What is the best way to generate a slug and directory for a new roadmap phase?

The best way to generate a phase directory and slug is to supply a clear phase description. The system parses and validates the description, automatically generating the slug and creating the corresponding directory in sync with the roadmap update.

Do I need to manually calculate the next phase number when extending a milestone?

No, you do not need to manually calculate the next phase number. The system automatically determines the next sequential integer phase number by ignoring decimals and appending the new phase entry to the end of the current milestone.

Can I update the roadmap structure and STATE.md at the same time for a new phase?

Yes, you can update the roadmap structure and STATE.md simultaneously. When adding a new phase, the workflow inserts the entry into the roadmap and evolves STATE.md in sync to eliminate manual repository state updates.

Why does my roadmap phase management workflow require updating STATE.md?

Updating STATE.md is required to maintain consistent repository state tracking. It records the roadmap evolution history each time a new milestone phase directory is created, ensuring your team has an accurate log of structural changes.