ticket-write

为工程任务生成或完善用户故事、需求与验收标准。

把需求写成工程师能直接做的 ticket：先写清用户故事，再列出需求和验收标准，确保能交付一个小而完整的工作单元。用在需要创建新功能、拆分大任务或把模糊需求交给开发者实现时最合适。特色是把意图、上下文和完成定义都写清楚，让读到的人不用当面问就能开始开发并知道何为“完成”。

A ticket is a single, self-contained **unit of work** — small enough that an
engineer can hold it in their head. It might be one slice of a larger feature
or stand on its own. Tickets are consumed by software engineers, often
asynchronously — the person who reads it can't lean over and ask what you meant.
So a good ticket carries enough intent, context, and a clear definition of done
that an engineer can start without a meeting, while still leaving room for their
judgement on *how* to build it.

Right-size the ticket to the work. A small change gets a short ticket — don't
pad it to look thorough. Some work genuinely needs a long ticket, but that's the
exception, not the default: a wall of te