What problem does it solve? Keeping a project Kanban board in sync with actual work is error-prone: agents forget transitions, write rows with the wrong column schema, or commit board edits to the wrong branch. This Skill standardizes every task lifecycle transition (In Progress, Blocked, Review, Done) across two board backends so board state always travels with the code it describes. ## Core Features & Use Cases - Dual-backend transitions: On the github backend it swaps status: labels via gh issue edit and relies on Closes #{issue} for Done; on the markdown backend it edits board-context.md with per-column schemas and commits the change on the task branch. - Full lifecycle coverage: Handles Ready → In Progress, In Progress → Blocked, Blocked → In Progress, In Progress → Review, and Review → Done, including metadata like blockers, reviewers, cycle days, and PR links. - Failure recovery: If the Done commit's re-triggered CI run fails, it resets the commit, force-pushes, moves the task back to Review, and hands off to /address-feedback with a 3-iteration cap. - Use Case: An agent finishes implementing task US-042 and says "send to review" — the Skill moves the task to Review, records the reviewer and PR number, and commits the board edit on the feature branch so it merges with the PR. ## Quick Start Ask the agent to update the board by moving task US-042 to Review with PR #47 attached.
