Ticket
A tracked unit of work with a bounded outcome and enough evidence to implement and verify it.
Illustrative conversation
- Can an agent implement this issue without asking what “done” means?
- Only if the ticket links the source context and includes concrete acceptance checks for the bounded change.
Definition
A ticket captures a specific piece of work so it can be prioritized, assigned, discussed, and closed. For agent-ready implementation it should state the desired outcome, in-scope and out-of-scope boundaries, links to the relevant spec and primary sources, dependencies, and acceptance checks. A ticket may reference a broader specification, but it should not silently replace missing product decisions.
Reviewed