Name: Backlog Update
Author: EvgeniiFenita

Backlog Management Playbook

Goal

Keep docs/backlog.yaml and docs/backlog-archive.yaml consistent by using scripts/backlog.py only.

use this skill when adding, editing, validating, or closing a backlog item
use this skill when you need to inspect the next candidate task from the backlog
do not use this skill for session-local todo tracking; use the session todo system for that

Never edit backlog YAML directly.
Keep tasks Open while you work; the backlog has no In Progress status.
Run python scripts/backlog.py validate after add / close operations and after any suspicious backlog state.
One logical change should usually map to one backlog task. Do not create extra backlog items for tiny same-scope follow-ups such as a matching doc fix, a skill tweak, or a closely related test adjustment if they are part of the same coherent slice.

Keep docs/backlog.yaml and docs/backlog-archive.yaml consistent by using scripts/backlog.py only.

use this skill when adding, editing, validating, or closing a backlog item
use this skill when you need to inspect the next candidate task from the backlog
do not use this skill for session-local todo tracking; use the session todo system for that

Never edit backlog YAML directly.
Keep tasks Open while you work; the backlog has no In Progress status.
Run python scripts/backlog.py validate after add / close operations and after any suspicious backlog state.
One logical change should usually map to one backlog task. Do not create extra backlog items for tiny same-scope follow-ups such as a matching doc fix, a skill tweak, or a closely related test adjustment if they are part of the same coherent slice.