backlog

Manages deferred work items in a centralized backlog.md registry with status transitions.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/ab300819/keel-workflow --skill backlog-ab300819
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backlog
Source: https://github.com/ab300819/keel-workflow/tree/main/skills/backlog
Command: npx skills add https://github.com/ab300819/keel-workflow --skill backlog-ab300819

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Deferred tasks in a documentation-driven development workflow often get lost or forgotten. This Skill provides a single source of truth (docs/devdocs/backlog.md) for parking, tracking, reactivating, and closing work items that are not yet ready for the current development cycle, without creating a new numbering system or duplicating Jira-style boards. ## Core Features & Use Cases - Park and Track Items: Register deferred items anchored to existing source IDs (F/US/AC/T/INS/BUG/FR/NFR/M) with a strict state machine (parked → reactivated / closed / superseded). - Reactivation Routing: Route reactivated entries to the correct downstream flow (requirements, dev-tasks, bugfix, insights, prd) with mandatory target_flow and target_id gating. - Schema Realignment: Migrate backlog.md structure across spec versions (backlog.v1 → v2) using a Migration Matrix with idempotent, structure-only fixes. - Use Case: During verification, a P3 edge-case issue is found but should not block the release. Park it via the backlog, then later reactivate it into dev-tasks as task T-08 when capacity allows. ## Quick Start Ask the AI to park a deferred item by running the backlog skill with a source ID, for example: park item F-01 into the backlog with a note explaining why it is deferred.

Frequently Asked Questions about backlog

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

FAQPage Schema
How do I park a deferred task in a development backlog?

Run the backlog skill with the park command and an existing source ID such as F-01 or AC-05. The entry is appended to docs/devdocs/backlog.md with status parked, a creation date, and the originating skill, without modifying the original source file.

How do I reactivate a parked backlog item?

Use the reactivate command with the source ID plus a target_flow and target_id, such as dev-tasks and T-08. Reactivation is blocked until both target fields are provided, ensuring the item lands in a concrete downstream flow.

Does this backlog replace Jira or Linear?

No. It deliberately avoids boards, swimlanes, assignees, prioritization, and sprint capacity management. It only maintains a traceable index of deferred items anchored to existing requirement and task IDs inside the repository documentation.

Can I create new backlog-specific IDs like B-001?

No. Creating new numbering schemes such as B-XXX is explicitly forbidden. Every entry must anchor to an existing source ID (F, US, AC, T, INS, BUG, FR, NFR), with M-XXX as the sole exception for ideas emerging mid-milestone.

What happens when the backlog file structure changes between versions?

The realign flow compares the file against the current spec_version Migration Matrix, lists structural gaps, asks for confirmation on restructuring changes, and backfills missing sections idempotently without altering business statuses.