roadmap

Generate a ROADMAP.md with vision, milestones, and short/medium/long term goals.

19|4|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/wunki/amplify --skill roadmap-wunki
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roadmap
Source: https://github.com/wunki/amplify/tree/main/skills/roadmap
Command: npx skills add https://github.com/wunki/amplify --skill roadmap-wunki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create a clear and actionable ROADMAP.md document, essential for communicating your open-source project's vision, current status, and future direction to potential contributors.

Core Features & Use Cases

  • Codebase Analysis: Automatically assesses project status by reviewing code, documentation, and issue trackers.
  • Structured Roadmap Generation: Creates a ROADMAP.md file with sections for Vision, How to Contribute, Timeline (Now/Next/Later/Future), Out of Scope, and Completed work.
  • Contributor Attraction: Helps define clear goals and areas where contributions are most welcome.

Quick Start

Use the roadmap skill to create a ROADMAP.md for the current project.

Frequently Asked Questions about roadmap

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

FAQPage Schema
How do I generate a ROADMAP.md for an open-source project?

To generate a ROADMAP.md, analyze the codebase, README, issue tracker, and changelog to infer project status. This structures the project's vision, milestones, and goals into a standardized document following open source conventions.

What should a project roadmap include to attract open source contributors?

A project roadmap should include a clear vision, a contribution guide, and a timeline organized into Now, Next, Later, and Future sections. Defining out-of-scope items and completed work also helps attract contributors by clarifying priorities.

How do I organize project milestones into short, medium, and long term goals?

You organize project milestones by analyzing documentation and code structure to infer current priorities, then categorizing upcoming work into a structured timeline. This separates immediate tasks from future objectives within the roadmap.

Can I create a project roadmap by analyzing an existing codebase and issue tracker?

Yes, you can create a project roadmap by analyzing an existing codebase and issue tracker. Reviewing the changelog, documentation, and code structure allows the system to infer project status and automatically generate a structured roadmap document.

What is the best way to communicate project vision and direction to potential contributors?

The best way to communicate project vision is by generating a ROADMAP.md that defines milestones and organizes work into clear phases. This structured document explicitly outlines where contributions are most welcome and what falls out of scope.