backlog-check

To clean outdated backlog items, you can validate `docs/dev/backlog.md` entries against current codebase status, checking if referenced files and symptoms still exist. Items are flagged for deletion and pruned after user confirmation.

Safe backlog pruning requires a two-phase process: running a dry-run to review suggested deletions, confirming per-item, then executing removals and re-sorting. Validation stops immediately if format errors occur.

Backlog verification inspects recent git history and codebase changes to assess whether referenced files, functions, or configs still exist and if described symptoms remain reproducible, ensuring documentation hygiene.

You need backlog consistency validation before any pruning operation to ensure required fields in `docs/dev/backlog.md` are present. Mandatory validation stops on format errors to prevent unsafe deletions.

Yes, backlog-check requires explicit user confirmation including per-item review before deleting any documentation entries. It performs a dry-run first, then prunes and sorts the backlog only after approval.

Backlog maintenance stops on format errors as a mandatory safety measure to prevent pruning valid items with missing fields. Validation checks required fields in `docs/dev/backlog.md` before proceeding to cleanup.