roadmap-analysis

ROADMAP.md analysis and management. Use for finding pending tasks and updating completion status.

⭐5stars🔀1forks📁View on GitHub🕐Updated Jan 11, 2026

When & Why to Use This Skill

This Claude skill automates the analysis and management of ROADMAP.md files, streamlining project tracking and task prioritization. It helps teams maintain an organized development lifecycle by identifying pending items, proposing next steps based on project phases, and ensuring consistent status updates across documentation.

Use Cases

  • Task Prioritization: Automatically identify and suggest the next three pending tasks from the current project phase to keep development moving.
  • Automated Progress Updates: Update the completion status of features in the ROADMAP.md file with standardized markdown formatting once tasks are finished.
  • Documentation Synchronization: Ensure consistency between the project roadmap and CHANGELOG.md by cross-referencing completed features and unreleased changes.
  • Workflow Standardization: Enforce clean roadmap structures by managing checkboxes and phase-based sections without manual formatting errors.
nameroadmap-analysis
descriptionROADMAP.md analysis and management. Use for finding pending tasks and updating completion status.

ROADMAP Analysis

1. ROADMAP.md Format

Checkboxes

  • [ ] - not done
  • [x] - completed

NO task numbers in ROADMAP!

  • Only feature/idea names
  • OpenSpec numbers go in openspec/changes/

2. Finding Pending Items

Search pattern

[ ]

Check current phase

  • Phase 0, Phase 1, etc.
  • Priority: top to bottom within section

3. Proposing Tasks

When user has no idea:

  1. Read ROADMAP.md
  2. Find current phase section
  3. Select 3 uncompleted items [ ]
  4. Present to user:
    Pending items from ROADMAP:
    1. [Item name] - brief description
    2. [Item name] - brief description
    3. [Item name] - brief description
    
    Which one would you like to work on?
    
  5. Wait for user selection

4. Updating ROADMAP

When feature is complete

Before:
- [ ] Add statistics panel

After:
- [x] Add statistics panel

Rules

  • ONLY mark [x] when feature is fully done
  • Do NOT add task numbers
  • Do NOT add OpenSpec references
  • Keep it simple: just checkboxes

5. ROADMAP Sections

Typical structure

# ROADMAP

## Phase 0 - Foundation
- [x] Project setup
- [x] Basic GUI
- [ ] Settings dialog

## Phase 1 - Core Editor
- [ ] Rich text editing
- [ ] Document structure
...

6. Cross-Reference with CHANGELOG

When updating ROADMAP:

  1. Also add entry to CHANGELOG.md [Unreleased]
  2. Use same feature name
  3. Keep descriptions consistent