Writing Tickets

Write clear, actionable tickets grounded in actual codebase investigation. Produces output readable by PMs and actionable by engineers.

Announce at start: "Using writing-tickets to [write/rewrite] [ticket type] for [topic]."

Inputs

Extract from the user's message:

• Ticket type: initiative, epic, story, spike, or rewrite of existing ticket
• Topic or ticket key: what to write about, or existing ticket to rewrite
• Mode: --autonomous (no user input, self-grills, runs to completion) or interactive (default)
• Output: --direct (write to Jira without previewing) or present-first (default)
• Scope: --with-subtasks (also break into child tickets after approval)

If ticket type is ambiguous, ask: "Should I write just the [epic/story], or also break it into sub-tasks?"

Flow