reconcile-backlog-sweep-plan

Reconcile backlog-sweep plan state.json and plan.md against GitHub PR statuses.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill reconcile-backlog-sweep-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reconcile-backlog-sweep-plan
Source: https://github.com/darylmcd/Roslyn-Backed-MCP/tree/main/.claude/skills/reconcile-backlog-sweep-plan
Command: npx skills add https://github.com/darylmcd/Roslyn-Backed-MCP --skill reconcile-backlog-sweep-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Walks a backlog-sweep plan's state.json and plan.md, reconciles PR status against reality, and ships the updates as a PR on a short-lived branch.

Core Features & Use Cases

  • Reconciles in-flight initiatives by querying GitHub PRs to determine merged/deferred/open states.
  • Updates state.json and plan.md to reflect actual PR outcomes, preventing re-shipping of already-merged work.
  • Automates branch creation, committing, and PR submission in a controlled, auditable workflow.

Quick Start

Run the backlog-sweep reconciliation to align state.json and plan.md with merged/deferred PRs.

Frequently Asked Questions about reconcile-backlog-sweep-plan

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

FAQPage Schema
How do I reconcile a backlog plan with GitHub PR status?

To reconcile a backlog plan with GitHub PR status, query the current state of each in-flight initiative's PR, compute whether it should transition to merged or deferred, and generate a dry-run diff to review before applying updates to your plan.

What is a backlog-sweep plan reconciliation?

A backlog-sweep plan reconciliation is the process of aligning state.json and plan.md files with actual GitHub PR outcomes, ensuring that already-merged work is not re-shipped and deferred items are tracked properly.

How do I update state.json and plan.md to reflect merged PRs?

You update state.json and plan.md by querying GitHub PR states for each candidate initiative, computing the appropriate transitions, and applying the edits through a controlled commit plan on a short-lived branch.

Does this reconciliation workflow require the gh CLI and git?

Yes, this workflow relies on the gh CLI to query GitHub PR state and git to guide branch creation, apply edits, and record a commit plan for subsequent PR-based shipping of the reconciled backlog updates.

Can I preview changes before applying them to the backlog plan?

Yes, you can preview changes because the reconciliation computes transitions and mirrors them into a dry-run diff without applying them, allowing you to review the proposed updates to state.json and plan.md before committing.

Why does my backlog plan still show open PRs that are already merged?

Your backlog plan shows open PRs that are already merged because state.json and plan.md have not been reconciled with actual GitHub PR outcomes, a mismatch this Skill resolves by querying PR states and preparing the correct transitions.