plan-roadmap

Name: plan-roadmap
Availability: InStock
Author: TypeMD

Plan weekly GitHub release roadmaps by balancing issue scope and dependencies.

9|2|Updated Mar 4, 2026

Search Tags:#planning #github #roadmap #release #issue #dependency #cadence

Ready to run

npx skills add https://github.com/typemd/typemd --skill plan-roadmap-typemd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-roadmap
Source: https://github.com/typemd/typemd/tree/main/.claude/skills/plan-roadmap
Command: npx skills add https://github.com/typemd/typemd --skill plan-roadmap-typemd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning release roadmaps manually leads to uneven workload, missed dependencies, and releases that exceed a one‑week cadence. This Skill automates gathering Release issues, analyzing relationships, and rebalancing scope to ensure each weekly release delivers visible value.

Core Features & Use Cases

Gather all Release issues and their sub‑issues from a GitHub repository.
Analyze parent‑child, blocking, and epic relationships to identify orphaned or stale issues.
Define themed releases for the next five weeks and suggest issue allocations respecting effort budgets.
Move issues between releases, add or remove blocking relationships, and create new Release issues as needed.
Produce a final report of release contents and remaining blockers.

Quick Start

Plan a five‑week release roadmap with balanced scope for the TypeMD project.

Frequently Asked Questions about plan-roadmap

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

FAQPage Schema

How do I plan weekly release roadmaps for a GitHub repository?▼

To plan weekly release roadmaps, gather Release issues and sub-issues via GitHub CLI, analyze blocking dependencies, define themes for the next five weeks, and rebalance issue scope to ensure each weekly release delivers visible value.

What is the best way to balance issue scope across a one-week release cadence?▼

Balancing issue scope across a one-week release cadence involves analyzing parent-child and blocking relationships to identify orphaned issues, then moving issues between releases to respect effort budgets and prevent uneven workload.

Can I use GitHub issues to schedule work and track dependencies for a five-week release plan?▼

Yes, you can use GitHub Release-type issues and sub-issues to schedule work. The process fetches issues via GitHub API, analyzes epic relationships, and allocates issues across a five-week plan while respecting dependencies.

How does analyzing blocking relationships help prevent missed dependencies in release planning?▼

Analyzing blocking relationships in release planning identifies orphaned or stale issues early. By mapping parent-child and blocking dependencies, you can move issues between releases without breaking the dependency chain or exceeding the weekly cadence.

What's the best way to move issues between releases while respecting dependencies?▼

Moving issues between releases while respecting dependencies requires analyzing blocking relationships first, then reallocating issues to themed releases based on effort budgets, and adding or removing blocking links as needed to maintain a balanced weekly scope.