roadmap-guide

Automates creation and maintenance of concise decision-traceable roadmaps in docs/roadmap.md.

Updated Nov 7, 2025
One-click install
npx skills add https://github.com/MMorit00/fund-portfolio-bot --skill roadmap-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roadmap-guide
Source: https://github.com/MMorit00/fund-portfolio-bot/tree/main/.claude/skills/roadmap-guide
Command: npx skills add https://github.com/MMorit00/fund-portfolio-bot --skill roadmap-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Roadmap guidance that helps teams write, update, and maintain roadmap.md as a concise, decision-focused navigation document.

Core Features & Use Cases

  • When to use this guideline: add new versions, update statuses, record architectural decisions, and mark data-source limitations.
  • Principles: prioritizes brevity and clarity; avoids redundancy and unnecessary detail; supports version-entry structure and comparison.
  • Use Case: Imagine drafting a new version entry for docs/roadmap.md and documenting the rationale behind a key architectural decision.

Quick Start

Follow this guide when editing docs/roadmap.md to ensure concise, consistent entries.

Frequently Asked Questions about roadmap-guide

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

FAQPage Schema
How do I write and maintain a concise product roadmap document?

To write and maintain a concise product roadmap, use guided rules that structure version entries, update statuses, and record architectural decisions while avoiding redundancy. This ensures your roadmap stays decision-focused and easy to navigate.

What is the best way to document architectural decisions in a roadmap?

The best way to document architectural decisions in a roadmap is through decision-traceable entries. This approach records the rationale behind key changes directly within your version status updates, ensuring historical context is preserved.

Can I use this roadmap guidance to mark data-source restrictions?

Yes, you can use this roadmap guidance to mark data-source restrictions. It supports documenting specific limitations alongside version entries and architectural decisions, ensuring data constraints are visible and traceable.

What are the limitations of keeping a roadmap strictly concise?

The limitation of keeping a roadmap strictly concise is the omission of deep technical detail. By prioritizing brevity and clarity to avoid redundancy, the document serves as a navigation tool rather than a comprehensive technical specification.