reconcile-backlog

Proposes and applies an owner-approved hub taxonomy to reconcile an agenda backlog.

14|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/intendant-dev/Intendant --skill reconcile-backlog-intendant-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reconcile-backlog
Source: https://github.com/intendant-dev/Intendant/tree/main/automations/reconcile-backlog
Command: npx skills add https://github.com/intendant-dev/Intendant --skill reconcile-backlog-intendant-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large backlogs accumulate stale, duplicate, and unlinked items over time, and reorganizing them safely requires human judgment. This Skill structures that cleanup as a two-stage workflow: a survey session proposes a hub taxonomy, and nothing is applied until the owner explicitly acknowledges it. ## Core Features & Use Cases - Survey & Propose: Reads the entire agenda (open, done, and retired items) and drafts a hub taxonomy with item placements, relates_to pairs, and stale/duplicate flags, written into the survey item's body for review. - Human Approval Gate: The survey node stays open until the owner completes it; the apply node stays blocked until that acknowledgment, so no changes happen without consent. - Guarded Apply: The apply session builds exactly the acknowledged shape through attributed ops, honoring owner amendments (latest word wins) and using repair-by-annotation instead of editing or retiring other actors' items. - Use Case: A team running an Intendant agenda with hundreds of accumulated items uses this workflow to have an agent propose a hub structure, review it, and then have a second session apply the approved reorganization. ## Quick Start Run the reconcile-backlog workflow to survey my entire agenda, propose a hub taxonomy for my approval, and then apply the acknowledged structure.

Frequently Asked Questions about reconcile-backlog

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

FAQPage Schema
How do I reorganize a large backlog of agenda items into hubs?▼

Use a two-stage reconcile workflow: a survey session reads all open, done, and retired items and proposes a hub taxonomy with placements and relates_to pairs, then an apply session builds exactly that structure after owner approval. Nothing is created during the survey phase.

How does the human approval gate work in this workflow?▼

The survey node stays open until the owner completes it, and that completion is the acknowledgment gesture. The apply node declares relies_on the survey node, so it stays blocked until the owner acknowledges the proposal.

Can the owner modify the proposed taxonomy before it is applied?▼

Yes. The owner can amend the proposal via annotations on the survey item, and those amendments govern under a lex posterior rule where the latest owner word wins. The apply session follows the amended proposal exactly.

Does the apply session ever edit or delete existing backlog items?▼

No. The apply session follows repair-by-annotation: it never retires, completes, or edits another actor's items. Stale or duplicate items are flagged through annotations instead of being modified.

What are the limitations of automated backlog reconciliation?▼

The proposal quality depends on the survey session's reading of the full agenda, and nested hubs are bounded by the store's ancestry-cycle guard. The workflow also requires an owner to review and complete the survey node, so it cannot run fully unattended.