backlog

Records technical debt and deferred tasks as numbered Markdown files in docs/backlog.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/lfuuu/claude-rules --skill backlog-lfuuu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backlog
Source: https://github.com/lfuuu/claude-rules/tree/main/shared-skills/process/backlog
Command: npx skills add https://github.com/lfuuu/claude-rules --skill backlog-lfuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Technical compromises, TODO/FIXME comments, and deferred scope made during implementation or code review are easily forgotten. This Skill captures them as structured, numbered Markdown records in docs/backlog/ so known limitations and tech debt stay visible in the repository instead of being lost. ## Core Features & Use Cases - Structured debt records: Creates docs/backlog/NNN-slug.md files with frontmatter tracking status, category (limitation, optimization, refactor, ux, security, ops), priority, and source. - Lifecycle management: Subcommands add, list, start, done, wontfix, and show move entries through an open → in-progress → done/wontfix workflow. - Agent integration: Backend, frontend, reviewer, teamlead, and techwriter agents automatically log compromises and deferred findings during their work. - Use Case: During a review you find a non-blocking N+1 query. Run the add subcommand to file it as an optimization entry sourced from the reviewer, then close it months later with done and a PR link. ## Quick Start Ask the agent to add a backlog entry describing the technical compromise or limitation you just left in the code, including the file and line reference.

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 in a repository?

Use the add subcommand to create a numbered Markdown record in docs/backlog/ with category, priority, and source metadata. Entries are stored as plain files in the repo, so the debt log is versioned alongside the code it describes.

What is the difference between a backlog entry and a todo item?

A todo captures an idea in an incubator that may become a feature and requires a drill phase. A backlog entry records an already-made technical compromise, known limitation, or deferred scope discovered during implementation or review, with no drill step.

How do I filter the backlog by status or priority?

The list subcommand accepts filters such as open, in-progress, category=<cat>, or priority=high. It reads the YAML frontmatter of every docs/backlog file and renders a table with title, status, category, priority, source, and last-updated date.

Can coding agents log tech debt automatically during implementation?

Yes. Backend, frontend, devops, reviewer, teamlead, and techwriter agents are instructed to call the add subcommand whenever they leave a TODO/FIXME, accept a compromise, or defer scope, then continue their main work without interruption.

When should I mark a backlog entry as wontfix instead of done?

Use wontfix when the team decides the debt will not be addressed, providing a reason that is appended to a Decisions section. Use done when the work is completed, optionally attaching a PR or commit reference to the Implementation section.