backlog-reconcile

Reconcile project backlogs with deployed codebase states and update issue statuses.

1|Updated Mar 28, 2026

Search Tags:#project management #issue management #GitHub integration #codebase alignment #backlog reconciliation

Ready to run

npx skills add https://github.com/refluster/ai-native-article --skill backlog-reconcile

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backlog-reconcile
Source: https://github.com/refluster/ai-native-article/tree/main/workforce/skills/backlog-reconcile
Command: npx skills add https://github.com/refluster/ai-native-article --skill backlog-reconcile

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill ensures that project backlogs accurately reflect the state of the deployed codebase, reducing the drift between planning and reality.

Core Features & Use Cases

Backlog Reconciliation: Compares planning artifacts against deployed code to identify discrepancies.
Automatic Classification: Classifies items as 'done', 'in-progress', 'not started', 'obsoleted', or 'incidentally done'.
Issue Management: Closes, rewrites, splits, or files new issues based on the reconciliation results.
PR Generation: Generates a draft pull request with reconciliation updates.
Use Case: For a software project, use this Skill to reconcile epics and open issues with the latest code deployment, ensuring the backlog is up-to-date.

Quick Start

Run the backlog-reconcile skill for the current project to reconcile the backlog with the deployed codebase.

Frequently Asked Questions about backlog-reconcile

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

FAQPage Schema

How do I reconcile my project backlog with deployed codebase states?▼

To reconcile your project backlog with deployed codebase states, compare planning artifacts against the deployment to identify discrepancies and automatically classify items as done, in-progress, or obsoleted, then generate a draft pull request with the updates.

What is backlog reconciliation in software project management?▼

Backlog reconciliation is the process of comparing planning artifacts against deployed code to identify discrepancies, ensuring project backlogs accurately reflect reality and reducing drift between planning and the actual codebase state.

Do I need GitHub authentication to update issue statuses from a deployed codebase?▼

Yes, you need GitHub authentication to update issue statuses from a deployed codebase, as the reconciliation process requires GitHub integration to close, rewrite, split, or file new issues and generate draft pull requests.

How do I classify open issues as done or obsoleted after a code deployment?▼

You classify open issues by comparing them against the deployed codebase to automatically categorize items as done, in-progress, not started, obsoleted, or incidentally done, subsequently closing or rewriting the issues based on those results.

Can I automatically generate a pull request for backlog updates?▼

Yes, you can automatically generate a draft pull request for backlog updates, which packages the reconciliation results and issue management changes together for review and integration into the main project.

What are the limitations of automatic backlog reconciliation with GitHub?▼

The limitations of automatic backlog reconciliation include its dependency on GitHub authentication for issue and PR operations, meaning it cannot reconcile backlogs hosted on other issue management platforms or operate without proper GitHub integration.