Skip to Content
Cheat Sheet/work-ticket

/work-ticket

Pick up the top-priority ticket from the Ready column and ship it through the full chain — branch, implementation, tests, CI, review — without you having to babysit each step.

When to use it

This is the everyday command. You walk through the kanban in the morning, decide which ticket goes next, and type /work-ticket. The Ticket Worker agent picks the top-priority item from Ready, moves it to In Progress, creates a feature branch (feature/issue-{N}-{slug}), implements the change, runs lint and tests locally, pushes, opens a pull request, and — on green CI — auto-launches /review-pr so the reviewer agent has the next move ready. You watch this happen. That is the gemba walk: agents do the work, you watch the line.

If the worker takes a turn you disagree with — wrong abstraction, missed a guardrail, overthinks a simple change — interrupt and redirect. Specifying the next move (“simpler — just edit the existing function”) is the right correction, not “no don’t do that.” The worker resumes from your correction.

For changes too small to warrant ticket ceremony (a typo, a lint violation, a one-line config tweak), use /quick-fix instead — same branch + PR discipline, no board state changes.

How it fits

/groom-backlog fills Ready. /work-ticket picks the top item and ships it through CI to an approved PR. Only the human merges.

What it does (quick)

  • Verifies the ticket meets Definition of Ready (4 Power Sections + safety class + priority)
  • Creates the feature branch from main and moves the ticket to In Progress
  • Implements the change following CLAUDE.md standards and existing patterns
  • Runs lint and tests locally; never pushes with failing tests
  • Pushes to origin, opens a PR with a detailed body linked to the issue
  • Watches CI; auto-fixes failures up to 3 times before escalating
  • On green CI: moves the ticket to In Review and auto-launches /review-pr on the new PR
  • /groom-backlog — fills Ready before this command picks the top item
  • /quick-fix — the lightweight sibling for changes that don’t warrant full ticket ceremony
  • /swarm — when a ticket admits variation across an axis and you want N parallel implementations
  • /review-pr — auto-chained from /work-ticket on green CI per project policy

Canonical spec: .claude/commands/work-ticket.md

Last updated on
/check-milestone/quick-fix