backlog

Manages a tech debt backlog by adding, listing, resolving, prioritizing, and suggesting batch fixes for tracked issues.

6|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/greglas75/zuvo --skill backlog-greglas75
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backlog
Source: https://github.com/greglas75/zuvo/tree/main/skills/backlog
Command: npx skills add https://github.com/greglas75/zuvo --skill backlog-greglas75

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Technical debt findings from audits and code reviews get lost or duplicated without a central tracking system. This Skill maintains a single persistent backlog file (memory/backlog.md) where issues are recorded, deduplicated by fingerprint, prioritized, and resolved over time. ## Core Features & Use Cases - Backlog CRUD with deduplication: Add, list, fix, wontfix, delete, archive, and re-open items using fingerprint-based dedup keys so regressions are re-opened under the same ID instead of filed as new work. - Prioritization scoring: Ranks OPEN items with a (Impact + Risk) x (6 - Effort) formula, optionally enhanced by CodeSift reference counting to measure blast radius. - Batch suggestions: Groups items by pattern (same audit gate, same test pattern, same module) and proposes batch fix commands like zuvo:fix-tests or zuvo:refactor. - Use Case: After running a code audit that finds 12 issues, persist them to the backlog, run prioritize to rank them by urgency, then use suggest to get a batch fix plan for the 5 items sharing the same failure pattern. ## Quick Start Ask the AI to list the current tech debt backlog and add a new high-severity item describing a race condition in payout.service.ts.

Frequently Asked Questions about backlog

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

FAQPage Schema
How do I track technical debt found during code reviews?

Add each finding to the backlog with a file path, problem description, severity, and category. The skill assigns a sequential B-{N} ID and a fingerprint dedup key so repeated sightings update the existing entry instead of creating duplicates.

How to prioritize a tech debt backlog?

Run the prioritize mode, which scores each OPEN item with (Impact + Risk) x (6 - Effort), producing a ranked table from score 2 to 50. When CodeSift is indexed, reference counts increase Impact and Risk scores for widely-used code.

Does the backlog work inside git worktrees?

Yes, the backlog lives at the main checkout root, resolved via git worktree list with a git rev-parse fallback. The skill never creates a backlog inside a linked worktree and merges any legacy worktree-local copies into the main file.

What happens when a fixed issue reappears in the backlog?

The dedup lookup checks both the active backlog and the archive. An archived match is treated as a regression: it is re-opened under the same ID with a back-link and severity raised one band, never filed as a new item.

When should I archive versus delete backlog items?

Archive resolved entries once there are 50 or more resolved items or the file exceeds 100 KB; archiving preserves records so regressions are detected. Delete is destructive and discouraged because it destroys the record used for regression matching.