review-roadmap

Validate ROADMAP.md files for required fields, dependency integrity, and requirement coverage.

6|3|Updated Mar 31, 2026
One-click install
npx skills add https://github.com/alo-exp/silver-bullet --skill review-roadmap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-roadmap
Source: https://github.com/alo-exp/silver-bullet/tree/main/forge/skills/review-roadmap
Command: npx skills add https://github.com/alo-exp/silver-bullet --skill review-roadmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ROADMAP.md artifacts often lack consistent structure and complete fields, leading to misaligned plans and execution gaps. This skill enforces a standardized quality review against a defined roadmap quality criteria, catching missing fields, incomplete requirements, phantom entries, and dependency issues before work proceeds.

Core Features & Use Cases

  • Validates every phase for required fields (Goal, Depends on, Requirements, Success Criteria) to ensure completeness.
  • Checks 100% requirement coverage when a source requirements file is provided, preventing orphaned or phantom requirements.
  • Detects phantom references and circular dependencies, ensuring a correct, navigable roadmap.
  • Provides traceability ties between requirements and success criteria, and highlights missing or inconsistent plans.
  • Useful for product-management teams validating ROADMAP.md during planning, review cycles, or before major milestones.

Quick Start

Invoke the reviewer on ROADMAP.md by running /review-roadmap <roadmap-path>.

Frequently Asked Questions about review-roadmap

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

FAQPage Schema
How do I validate my ROADMAP.md for missing fields and dependency issues?

To validate a ROADMAP.md, use this skill to check required fields like Goal, Requirements, and Success Criteria, while detecting phantom references and circular dependencies to ensure roadmap completeness.

What is requirement coverage validation in a product roadmap?

Requirement coverage validation checks that every requirement from a source file is fully traced across roadmap phases, preventing orphaned or phantom requirements and ensuring complete plan traceability.

How do I check for circular dependencies and phantom references in a roadmap?

Checking for circular dependencies and phantom references involves reviewing the Depends on fields within each roadmap phase to ensure all cross-references are navigable and correctly defined.

Can I trace success criteria back to specific requirements during a roadmap review?

Yes, you can trace success criteria back to specific requirements by validating traceability ties within the roadmap, which highlights any missing or inconsistent plans between phases and source requirements.

Do I need a source requirements file to perform a roadmap quality assurance check?

A source requirements file is needed to execute the 100% requirement coverage check, but the skill can still validate standard phase fields and dependency structures within the ROADMAP.md without one.

Why does my roadmap quality check fail on missing success criteria?

A roadmap quality check fails on missing success criteria because the validation enforces standardized completeness, requiring every phase to define Goal, Depends on, Requirements, and Success Criteria fields.