backlog-reconcile

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.

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.

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.

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.

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.

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.