When does this skill automatically trigger?

It triggers when editing files containing 'roadmap.md', when commit messages include terms like 'roadmap' or 'version', or when a user specifically asks for a roadmap update.

What is the core principle of the Roadmap Guide skill?

The core principle is that a roadmap should be a navigation map, not a textbook. It prioritizes high information density and brevity over detailed technical explanations.

How does it handle code snippets in roadmaps?

The skill enforces a strict rule to limit code examples to 5 lines or fewer, or remove them entirely if they don't contribute directly to understanding the high-level goal.

Does this skill help with architectural visualization?

Yes, it encourages and provides templates for ASCII diagrams to visualize data flows and system architecture within the documentation.

Roadmap Guide

Name: Roadmap Guide
Author: MMorit00

byMMorit00

Content Management

Enforces high-density, standardized project roadmaps by providing structured templates and brevity guidelines for documentation.

About

The Roadmap Guide skill is designed to transform project roadmaps from bloated technical manuals into clear, actionable navigation tools. It automates the standardization of roadmap.md files, ensuring that information density is prioritized over unnecessary detail. By providing rigid structures for versioning, status tracking, and architectural decision logging, this skill helps developers maintain a professional project trajectory while preventing scope creep and redundant documentation. It is particularly useful for teams that need to communicate high-level goals and limitations without burying them in implementation specifics.

Key Features

Brevity enforcement to keep descriptions under three lines and code examples minimal
Comparison table generators for highlighting differences between software releases
Standardized versioning structure with status markers (Completed, In Progress, Planned)
0 GitHub stars
Pre-defined templates for tracking 'What Not To Do' and project limitations
Support for ASCII-based architectural diagrams and data flow visualization

Use Cases

Documenting architectural decisions and scope exclusions to prevent feature creep
Updating project roadmaps with new feature plans and version milestones
Standardizing documentation across multiple repositories to maintain a consistent style

About

Key Features

Brevity enforcement to keep descriptions under three lines and code examples minimal
Comparison table generators for highlighting differences between software releases
Standardized versioning structure with status markers (Completed, In Progress, Planned)
0 GitHub stars
Pre-defined templates for tracking 'What Not To Do' and project limitations
Support for ASCII-based architectural diagrams and data flow visualization

Use Cases

Documenting architectural decisions and scope exclusions to prevent feature creep
Updating project roadmaps with new feature plans and version milestones
Standardizing documentation across multiple repositories to maintain a consistent style