Use when the user asks to add a phase, feature, or scope to the end of the current milestone roadmap. Adds the next sequential phase directory, updates ROADMAP.md, and tracks the change in STATE.md.
Installs into .claude/skills of the current project.
Are you the author of Gsd Add Phase?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/coco-research-gsd-add-phase)
---
name: gsd-add-phase
description: "Use when the user asks to add a phase, feature, or scope to the end of the current milestone roadmap. Adds the next sequential phase directory, updates ROADMAP.md, and tracks the change in STATE.md."
argument-hint: "<description>"
allowed-tools:
- Read
- Write
- Bash
---
<objective>
Add a new integer phase to the end of the current milestone in the roadmap.
Routes to the add-phase workflow which handles:
- Phase number calculation (next sequential integer)
- Directory creation with slug generation
- Roadmap structure updates
- STATE.md roadmap evolution tracking
</objective>
<execution_context>
@$HOME/.claude/get-shit-done/workflows/add-phase.md
</execution_context>
<context>
Arguments: $ARGUMENTS (phase description)
Roadmap and state are resolved in-workflow via `init phase-op` and targeted tool calls.
</context>
<process>
**Follow the add-phase workflow** from `@$HOME/.claude/get-shit-done/workflows/add-phase.md`.
The workflow handles all logic including:
1. Argument parsing and validation
2. Roadmap existence checking
3. Current milestone identification
4. Next phase number calculation (ignoring decimals)
5. Slug generation from description
6. Phase directory creation
7. Roadmap entry insertion
8. STATE.md updates
</process>
