write-tickets

Essential Principles

• Consistent structure. Predictable tickets are faster to read, estimate, and pick up - so every ticket follows the template for its type: same sections, same order, every time.
• Complete before quick. Tickets filed fast with sections missing bounce back with questions, so fill every relevant section - fill what you can from context, ask for the rest, and never silently drop one.
• Clear, testable acceptance criteria. Each criterion is independently verifiable. "Works correctly" is not a criterion.
• Pre-identify solutions where the path isn't obvious. Offer 1-3 real options with different tradeoffs so reviewers can decide direction before work starts. Skip the section when there's only one sensible approach - don't pad with "fix the bug".
• Tracker-agnostic content. Produce the ticket body plus generic field values (Title, Type, Parent/Project, Labels). Submission belongs to the tracker's own tool - see Related Skills.

Intake

What would you like to do?

1. Write a Story - new feature or capability
2. Write a Bug - a defect with reproduction steps
3. Write a Spike - a timeboxed investigation with a documented output
4. Audit a ticket - check an existing ticket against the readiness checklist and improve it