ticket-writinglisted

# Ticket Writing Transform an informal task description into a complete, actionable Jira ticket. ## Rules 1. Be specific — replace vague terms with concrete details 2. Infer reasonable context based on common software practices 3. Use Given/When/Then format for acceptance criteria 4. If critical information is missing, list clarifying questions at the end 5. Keep everything actionable and testable ## Codebase research Before generating the ticket, assess whether you have enough context. If the task mentions specific components, services, or modules you're unfamiliar with; existing functionality that needs modification; technical terms or domain concepts unique to this project; or files, APIs, or systems that require understanding — search the currently open project first: - Relevant source files and their structure - Existing implementations of similar features - Related tests that reveal expected behavior - README files or documentation - Configuration files that might be relevant Use what you find to make the ticket more specific and accurate. ## Output structure ```markdown ## Summary [One clear sentence describing what needs to be done] ## User Story As a [specific role/persona], I want [specific goal/action], so that [measurable benefit/value]. ### Background [Why this task exists, business context, problem being solved] ### Technical Context [Relevant findings from codebase research — existing patterns, related files, dependencies. Omit if no codebase search