Skip to Content
Cheat Sheet/create-ticket

/create-ticket

Create a single well-structured ticket that meets the project’s Definition of Ready — the four Power Sections, an effort estimate, a priority, and a safety class — without you having to remember the shape from memory.

When to use it

Use this when a feature request, bug report, or work item arrives and needs to go on the board. The command walks you through a guided workflow: it asks clarifying questions about the change, reads docs/TECHNICAL-ARCHITECTURE.md and docs/PRODUCT-REQUIREMENTS.md to pre-fill the Environment Context and Guardrails sections, searches existing issues to catch duplicates, drafts a ticket against the canonical format, and only then opens the GitHub issue. The output is a ticket that /work-ticket can pick up without further refinement.

Use this for single tickets you’ve decided to add. For deciding whether a feature is worth building at all, run /evaluate-feature first — that command produces a BUILD verdict that hands off to this one. For batch prioritization across the whole backlog, use /groom-backlog.

Don’t bypass this for “small” changes that lack the ceremony of a linked ticket — that’s what /quick-fix is for. The split is intentional: tickets carry context that survives across sessions; quick fixes are the lightweight path when there’s nothing worth carrying.

How it fits

Sources are either a direct request or a BUILD verdict from /evaluate-feature. Output lands in Backlog, where /groom-backlog later promotes it to Ready.

What it does (quick)

  • Verifies gh CLI auth, repo access, and project-board access (pre-flight)
  • Asks clarifying questions about the change to populate sections A–D
  • Reads docs/TECHNICAL-ARCHITECTURE.md and docs/PRODUCT-REQUIREMENTS.md to pre-fill Environment Context and Guardrails
  • Searches existing issues to surface duplicates before creating
  • Drafts the ticket per docs/TICKET-FORMAT.md (4 Power Sections, effort estimate, priority, safety class)
  • Self-checks the draft against the format before showing it to you
  • Creates the GitHub issue and adds it to the project board in Backlog
  • /evaluate-feature — upstream; a BUILD verdict feeds directly into this command
  • /groom-backlog — downstream; the natural next gate that decides when this ticket reaches Ready
  • /quick-fix — the lightweight alternative for changes too small for ticket ceremony

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

Last updated on
/upgrade/groom-backlog