What problem does it solve? Teams lose track of work when tasks are created without being added to the project board, branches are duplicated, or commits carry the wrong author. This Skill enforces a disciplined sequence — task creation, board placement, branch naming, column moves, and bot-signed commits — so every edit is traceable from board card to merged PR. ## Core Features & Use Cases - Four-step task creation: Runs npm run task:new to create the issue, embed its number in the title, add it to the board, and place it in the first column, with duplicate detection via issue search. - Branch and column discipline: Creates branches named <KEY>-<number>-<slug> from the epic branch and moves the task column (in-progress, in-review) immediately after each step. - Bot-signed commits: Commits with machine-account author/committer environment variables, conventional type(scope): description subjects, and explicit per-file staging verified with git diff --cached. - Use Case: Before starting a bug fix, ask the assistant to create the task, branch, and first commit — it checks the queue for duplicates, verifies board placement, and signs the commit as the bot account. ## Quick Start Create a task on the board, start a branch for it, and prepare a signed commit for my current changes following the git-workflow-commit pattern.
