Skip to content

a5c-ai/babysitter / library/methodologies/gsd/skills/roadmap-management

roadmap-management

Verified

Roadmap parsing, analysis, and mutation operations for ROADMAP.md. Handles phase and milestone lifecycle including add, insert (decimal), remove, complete, and requirements coverage analysis.

FileKindSize
README.mdmarkdown1.6 KB
SKILL.mdskill md8.7 KB
# roadmap-management

Roadmap parsing, phase operations, and requirements coverage analysis for GSD projects.

## Quick Start

ROADMAP.md is the master plan. This skill reads, modifies, and analyzes the roadmap.

### Parse the Roadmap

Read `.planning/ROADMAP.md` and extract milestones, phases, statuses, and requirement mappings.

### Add a Phase

Append a new phase at the end of the current milestone with the next sequential number.

### Insert a Decimal Phase

Insert urgent work between existing phases (e.g., Phase 72.1 between 72 and 73).

### Check Requirements Coverage

Verify every requirement in REQUIREMENTS.md is mapped to at least one phase.

## Examples

### Roadmap Structure

```markdown
## Milestone v1.0: MVP

### Phase 70: Setup
- **Status**: completed
- **Requirements**: R1, R2

### Phase 71: Database
- **Status**: in-progress
- **Requirements**: R3, R4
```

### Phase Status Flow

`planned` -> `in-progress` -> `completed` -> `verified`

### Coverage Report

```
Requirements: 13 total
Mapped: 13 (100%)
Gaps: none
```

## Troubleshooting

### Phase numbering is wrong after removal
- Phase removal triggers automatic renumbering
- Check that all references to old phase numbers have been updated
- Run `gsd health` to verify roadmap consistency

### Cannot remove a phase
- Only `planned` phases can be removed
- In-progress and completed phases are protected
- Complete the phase first or mark it as skipped

### Requirements coverage below 100%
- List unmapped requirements with `coverage_analysis()`
- Add new phases or update existing phases to cover gaps
- Newly added requirements after initial roadmap creation need manual mapping
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 198kUpdated Claude CodeCodexVerifiedInstall