ticket-new

Create a Ticket

Use the conversation context to draft and create a ticket in the issue tracker.

$ARGUMENTS

Ticket title

Short, imperative, specific (e.g., "Add retry logic to payment webhook handler")

Ticket Description

• Context: 1-2 sentences on why this matters
• Problem / Current behavior: What's wrong or missing today
• Desired outcome: What should be true after this is done
• Acceptance criteria: Concrete, verifiable checklist items
• Technical notes (optional): Code pointers, implementation hints, constraints

Writing Style

• Write like a "Product Engineer", not a PM writing a PRD. Be direct and specific, but make sure the business context and "WHY" is captured.
• Prefer concrete code references over abstract descriptions (e.g., "processWebhook() in src/webhooks/handler.ts" not "the webhook processing logic").
• Omit sections that have no content — don't include empty headings or filler.
• A good ticket is one a developer can pick up and start working on without asking follow-up questions.
• Make sure to not dictate to the implementor details how to solve it, at most point at relevant areas of the system
• Write the description as if nothing has been implemented yet — even when the work is already underway or finished in this session. This is not a formality: a ticket that narrates its own progress is unreadable a week later, and the board already tracks progress in the status field.
  • Describe the problem and the desired outcome. Never the work done against them.
  • Banned: "already done in branch X", "remaining work", "we changed Y", "this fixed Z", past tense about the fix, links to the session's branch or MR, and any "as discussed" framing.
  • Acceptance criteria are written as still-open, never pre-checked.
  • If the session revealed a constraint or a code pointer worth keeping, state it as a technical note about the system, not as a report of what we tried.

Division of labor

You (the orchestrator) write the ticket body yourself — never a subagent. The title and the description come from the conversation you are holding, and no subagent can see it.