roadmap-tracker

Synchronize roadmap progress and completion evidence across plan-driven epics.

18|Updated Feb 14, 2020
One-click install
npx skills add https://github.com/subroh0508/colormaster --skill roadmap-tracker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roadmap-tracker
Source: https://github.com/subroh0508/colormaster/tree/main/.claude/skills/roadmap-tracker
Command: npx skills add https://github.com/subroh0508/colormaster --skill roadmap-tracker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps roadmap status, completion evidence, blockers, and sequencing decisions synchronized across plan-driven work so teams do not lose track of what is done, what is blocked, and what should happen next.

Core Features & Use Cases

  • Roadmap Synchronization: Mirrors progress from plan and epic sources into dedicated roadmap files without writing back to the source plan.
  • Evidence Tracking: Records merge dates, pull request references, commit hashes, open questions, blockers, and step-order changes in a durable history.
  • Next-Step Prioritization: Recomputes the next recommended items by checking dependencies, current work overlap, and parallel execution potential.
  • Use Case: When an epic PR is merged, this Skill updates the epic roadmap, marks the phase complete, appends the evidence entry, and refreshes the recommended next tasks.

Quick Start

Ask the roadmap-tracker skill to update the roadmap from the latest plan and epic progress, then show the next recommended items.

Frequently Asked Questions about roadmap-tracker

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

FAQPage Schema
How do I sync epic progress and pull request evidence into a roadmap automatically?

Roadmap progress synchronization mirrors merge dates, pull request references, and commit hashes from plan-driven epics into dedicated roadmap files without writing back to the source plan. It appends completion evidence to a durable history and refreshes recommended next tasks automatically.

What is the best way to track blockers and open questions for active development epics?

Tracking blockers and open questions for active development involves recording them in a durable, append-only history within dedicated roadmap files. The roadmap tracker preserves this evidence alongside merge dates and step-order changes to maintain an accurate project status log.

How do I recompute next-step prioritization for roadmap items with dependencies?

Next-step prioritization recomputes recommended items by checking epic dependencies, current work overlap, and parallel execution potential. This dependency-aware recommendation resolves the optimal sequence for upcoming development tasks without modifying the original plan metadata.

Does roadmap tracking work without modifying the original plan source files?

Roadmap tracking operates strictly without writing back to source plans. It reads plan and epic metadata to synchronize progress and completion evidence into dedicated roadmap files, ensuring the original planning documents remain immutable while preserving an append-only history.

Can I visualize GitHub dependencies and roadmap progress using mermaid diagrams?

Visualizing GitHub dependencies and roadmap progress requires reading plan and epic metadata to map sequencing decisions. The tracker resolves dependency-aware recommendations and tracks completion evidence, which can be structured for rendering visualization diagrams.

Why should I not manually update roadmap status after a pull request merge?

Manually updating roadmap status after a pull request merge risks losing track of completion evidence and sequencing decisions. Automated synchronization appends merge dates and commit hashes to a durable history, ensuring accurate blocker tracking and next-step prioritization without human error.