to-tickets

Research the codebase for relevant files and patterns before writing tickets. Infer logical units of work from the conversation.

For each ticket, output two blocks separated by a blank line:

First block:

• Title — clear, actionable
• Description — brief, functional summary
• User story — "As a [role], I want [goal], so that [benefit]"
• Acceptance criteria — Given/When/Then format
• Subtasks — only if needed; use [ ] checkboxes

Second block: Estimates:

• Junior: X points, Xh
• Medior: X points, Xh
• Senior: X points, Xh

Business value: X/10