backlog

Create and archive backlog items with deterministic IDs and duplicate checks.

121|3|Updated Jan 13, 2022
One-click install
npx skills add https://github.com/jiangzhe/doradb --skill backlog-jiangzhe
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backlog
Source: https://github.com/jiangzhe/doradb/tree/main/.codex/skills/backlog
Command: npx skills add https://github.com/jiangzhe/doradb --skill backlog-jiangzhe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manage backlog todo documents in docs/backlogs with deterministic tooling. Use when manually creating backlog items with duplicate checks, or closing/archiving backlog items with explicit reasons.

Core Features & Use Cases

  • Deterministic id-based backlog item creation with duplicate checks to prevent duplication.
  • Lifecycle management for open and closed backlog docs with explicit close reasons.
  • Safe, auditable archival by moving completed items to the closed folder.

Quick Start

Create a new backlog item with a unique id, check for duplicates against open items, and save it under docs/backlogs.

Frequently Asked Questions about backlog

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

FAQPage Schema
How do I create backlog items with duplicate detection in docs?

Backlog item creation uses deterministic ID generation and duplicate checks against open items to prevent redundancy before saving under docs/backlogs.

What is the best way to manage backlog lifecycle and archive completed items?

Backlog lifecycle management tracks open and closed states, requiring explicit close reasons before safely moving completed docs to the closed folder for auditable archival.

How do I close and archive backlog docs with an explicit reason?

Closing backlog docs requires capturing an explicit reason, then moving the item from the open to the closed directory to ensure safe and auditable archival.

Does backlog management require local tooling scripts for deterministic commands?

Yes, deterministic backlog management requires local tooling scripts to execute the commands needed to create, locate, and move backlog docs between open and closed directories.

Why do I need deterministic IDs for backlog workflow automation?

Deterministic IDs ensure unique backlog item identification, enabling reliable duplicate detection and precise item location across open and closed lifecycle stages.