roadmap-refinement

Audit GitHub backlogs and project boards for stale items and drift.

2|1|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/solo-ist/prose --skill roadmap-refinement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: roadmap-refinement
Source: https://github.com/solo-ist/prose/tree/main/.claude/skills/roadmap-refinement
Command: npx skills add https://github.com/solo-ist/prose --skill roadmap-refinement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit the backlog and project board to identify stale items, board drift, and opportunities for bulk cleanup, helping teams stay aligned and productive.

Core Features & Use Cases

  • Backlog health checks: cross-check issues, PRs, and project items to surface items needing review or closure.
  • Board drift detection: compare open issues against the project board to surface missing or miscategorized items.
  • Approval-ready reports: generate a concise findings report for stakeholder review and bulk-change actions.

Quick Start

Invoke the /roadmap-refinement command to audit the backlog and present findings for approval.

Frequently Asked Questions about roadmap-refinement

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

FAQPage Schema
How do I audit a GitHub project backlog for stale issues and board drift?

To audit a GitHub backlog for stale issues and board drift, cross-reference issues, PRs, and project board items via gh CLI commands to surface candidates needing closure or re-prioritization.

What is the best way to find open issues missing from a GitHub project board?

Finding open issues missing from a GitHub project board requires comparing open issues against current project items to surface miscategorized work and generate a structured cleanup report.

Do I need the gh CLI to cross-reference issues and PRs for backlog health checks?

Yes, backlog health checks require the gh CLI to automate state gathering, cross-reference issues and PRs against project board items, and identify cleanup opportunities across open work.

Can I bulk close stale GitHub backlog items directly from the generated audit report?

The generated audit report outputs structured findings for stakeholder review and approval, enabling product teams to execute subsequent bulk-change actions for closing or re-prioritization.

When should I run a backlog audit to keep roadmaps clean and boards in sync?

Run a backlog audit when project boards accumulate drift, open work lacks categorization, or product teams need structured cleanup reports to realign roadmaps and re-prioritize stale items.