vibe-roadmap

Assign GitHub issues to milestones and roadmap labels via gh.

6|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-roadmap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-roadmap
Source: https://github.com/jacobcy/vibe-coding-control-center/tree/main/skills/vibe-roadmap
Command: npx skills add https://github.com/jacobcy/vibe-coding-control-center --skill vibe-roadmap

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Help teams decide which repository issues belong to which release windows by providing a consistent, label-driven roadmap triage process that assigns milestones, roadmap/* labels, and fine-grained priority tags so planning decisions are traceable and GitHub remains the source of truth.

Core Features & Use Cases

  • Label-driven Triage: Classify issues into roadmap buckets (roadmap/p0, roadmap/p1, roadmap/p2, roadmap/next, roadmap/future) and apply priority/[0-9] for intra-bucket ordering.
  • Milestone Assignment: Suggest and apply Milestone assignments to define version goals and release windows.
  • Intake Gate Decisions: Evaluate whether new repo issues should be included in the planning pool, deferred, or escalated for human discussion.
  • Use Case: Triage a set of new issues after a planning session to produce a candidate roadmap for the next release and label each item with milestone and priority metadata.

Quick Start

Use /vibe-roadmap to triage an issue by determining its milestone and applying the appropriate roadmap/* and priority/[0-9] labels.

Frequently Asked Questions about vibe-roadmap

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

FAQPage Schema
How do I prioritize GitHub issues for a project roadmap using labels?

To prioritize GitHub issues for a project roadmap, you can apply label-driven triage by assigning roadmap/* buckets and priority/[0-9] tags to rank items within each bucket. This ensures planning decisions are traceable and GitHub remains the source of truth.

What is the best way to assign GitHub issues to milestones for release planning?

The best way to assign GitHub issues to milestones for release planning is to evaluate issue states via the GitHub API and apply milestone assignments to define clear version goals and release windows.

How do I triage a backlog of GitHub issues to decide what goes into the next release?

You can triage a backlog of GitHub issues to decide what goes into the next release by applying an intake gate decision process, evaluating whether new issues should be included in the planning pool, deferred, or escalated.

Can I manage GitHub roadmap triage without local state persistence?

Yes, you can manage GitHub roadmap triage without local state persistence by reading issue and milestone states via the gh CLI and applying remote writes directly to GitHub, ensuring GitHub remains the single source of truth.

What do the roadmap p0, p1, and p2 labels mean for issue management?

In issue management, roadmap p0, p1, and p2 labels represent distinct roadmap buckets for classifying issues by priority. P0 indicates immediate priority, while p2 and buckets like next or future defer issues to later release windows.