backlog-ops

You can update backlog item statuses and acceptance criteria by applying staged-only file edits without auto-committing. This applies lifecycle operations in place, letting you commit backlog changes together with related code updates.

Epic status cascade consistency automatically aligns the parent epic's README table-of-contents with the derived state from its substories. It also includes drift detection to correct any mismatches based on repository backlog conventions.

Yes, backlog operations support pull, tick, and complete actions for specific item IDs including letter-suffixed substories. The system enforces strict preconditions and avoids guessing which checkbox to tick, requiring explicit user intent.

Strict guardrails prevent silent force-completion to avoid guessing which checkbox to tick. The system requires unchecked boxes to be addressed explicitly, correcting mismatches while asking for user intent when needed to maintain backlog integrity.

No, backlog-ops explicitly prevents out-of-scope operations like creating items. It focuses strictly on applying lifecycle operations such as status transitions, acceptance criteria updates, and TOC sorting to existing backlog entries.

You need a repository with established backlog conventions including item files, a backlog README with a table-of-contents, and defined epic cascade rules. The workflow requires consistent TOC movement and strict preconditions on current item statuses.