backlog-opslisted

<!-- Source: https://github.com/xxthunder/xxthunder-agentic-skills/tree/develop/plugins/xxthunder-dev-skills/skills/backlog-ops --> # Backlog Operations Mechanical lifecycle operations on a single backlog item: **pull**, **check** (tick an AC/UAT box), **complete**. Every operation keeps the item file and the `README.md` table of contents consistent and respects the epic-status cascade described in [references/epic-cascade.md](references/epic-cascade.md). This skill **stages file edits only**. It never creates a commit. Commits are the user's call (typically via the `commit-helper` skill) so the backlog change can ride in the same commit as the code change that justifies it. ## When This Skill Triggers | Trigger phrase | Operation | Section | |-------------------------------------------------|-----------|-----------------------------------| | "start XAS-025", "pull XAS-025", "begin XAS-025" | pull | [Pull](#pull-open--in-progress) | | "mark AC 2 done on XAS-025", "tick AC 1 for XAS-025", "check UAT 3 on XAS-025" | check | [Check](#check-tick-an-acuat-box) | | "close XAS-025", "complete XAS-025", "finish XAS-025", "mark XAS-025 done" | complete | [Complete](#complete-in-progress--done) | Do **not** trigger on refinement phrases ("let's refine", "add a new story") — those belong to the `refinement` skill. ## Core Assumptions The skill assumes the backlog follows the format documented by the `refineme