backlog-update

Govern backlog items across Librova YAML files using Backlog.py CLI.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/EvgeniiFenita/Librova --skill backlog-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backlog-update
Source: https://github.com/EvgeniiFenita/Librova/tree/main/.agents/skills/backlog-update
Command: npx skills add https://github.com/EvgeniiFenita/Librova --skill backlog-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Backlog management in Librova is prone to drift when edits are made directly in YAML files. This Skill provides a centralized playbook for adding, updating, validating, or closing backlog items, ensuring consistency across docs/backlog.yaml and docs/backlog-archive.yaml.

Core Features & Use Cases

  • Centralized backlog governance via Backlog.py commands: list, show, add, close, edit, reopen, sync-last-id, and validate.
  • Enforced workflow rules and integrity checks to prevent out-of-sync states.
  • Clear guidance on when to create, modify, or close backlog tasks and how to audit changes.

Quick Start

Run python scripts/Backlog.py list to view the current open backlog items.

Frequently Asked Questions about backlog-update

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

FAQPage Schema
How do I manage backlog items stored in YAML files without causing data drift?

Backlog management in YAML files requires a centralized CLI to govern changes. Using a Python script to apply workflow rules and integrity checks prevents out-of-sync states between active and archive files.

What's the best way to validate backlog tasks for consistency across multiple files?

Validating backlog tasks for consistency is done by running a validate command via the Backlog.py CLI. This inspects the YAML storage files to enforce workflow rules and prevent out-of-sync states across the repository.

How do I add and close tasks in a YAML backlog using Python?

Adding and closing tasks in a YAML backlog is handled by running specific add and close commands through the Python CLI. This workflow synchronizes items between the active backlog and archive YAML files.

Do I need a specific repository structure to run backlog validation scripts?

Yes, backlog validation scripts require running from the repository root. The Python CLI depends on specific YAML storage files, namely docs/backlog.yaml and docs/backlog-archive.yaml, to execute integrity checks properly.

Can I reopen a closed backlog task after it has been archived?

Yes, you can reopen a closed backlog task by running the reopen command in the Backlog.py CLI. This reverses the closure and synchronizes the item back from the archive file into the active backlog.