curate-backlog

Automate editorial curation of BACKLOG.md with deterministic heuristics and previews.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/fppfurtado/pragmatic-dev-toolkit --skill curate-backlog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: curate-backlog
Source: https://github.com/fppfurtado/pragmatic-dev-toolkit/tree/main/skills/curate-backlog
Command: npx skills add https://github.com/fppfurtado/pragmatic-dev-toolkit --skill curate-backlog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Curate and sanitize the project backlog by applying deterministic editorial heuristics and a non-destructive preview workflow, ensuring BACKLOG.md stays aligned with current priorities without disrupting ongoing work.

Core Features & Use Cases

  • Apply four detection heuristics to identify stale, urgent, or conflicting backlog items and propose concrete edits.
  • Preview changes before applying them, with cross-references to ADRs and notes to preserve governance.
  • Coordinate across branches and worktrees, supporting local sessions and forge workflows for remote coordination.

Quick Start

Curators invoke the backlog curation to preview and apply safe edits to BACKLOG.md when preparing for a backlog sweep.

Frequently Asked Questions about curate-backlog

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

FAQPage Schema
How do I automate backlog curation for a BACKLOG.md file?

Automating backlog curation applies deterministic editorial heuristics to identify stale or conflicting items in BACKLOG.md, proposing concrete edits while preserving governance through ADR cross-references.

What's the best way to preview backlog changes without disrupting ongoing work?

Preview backlog changes using a non-destructive preview workflow that requires a clean working tree, ensuring proposed edits to BACKLOG.md can be reviewed safely before application across branches.

Can I coordinate backlog sweeps across git worktrees and remote forks?

Yes, backlog sweeps coordinate across git worktrees and branches using local sessions and forge workflows, enabling remote coordination for editorial curation outside the normal session flow.

What signals are needed to identify stale or urgent backlog items?

Identifying stale or urgent backlog items requires access to ADRs and NOTES.md signals, applying four detection heuristics to evaluate entries against current project priorities and architectural decisions.

Do I need a clean working tree to apply backlog governance edits?

Yes, applying backlog governance edits requires a clean working tree to ensure non-destructive previews function correctly and proposed changes align with ADR integration without disrupting ongoing work.