Ticket
Tiket
A unit of work small enough to be scoped, done, and checked.
A ticket scopes one piece of work: what should change, what it depends on, and what counts as done. It is the unit that makes agent work tractable, because a task with a clear boundary can be attempted, finished, and verified without a human steering every step.
A good ticket names the observable outcome rather than the implementation. "Add a retry to the upload endpoint, max 3 attempts, exponential backoff" is a ticket. "Make uploads more robust" is a wish.
The other half of the ticket is the definition of done: the test that proves it, the check that the code compiles, the screenshot that shows the behaviour. A ticket without one is a suggestion.
Related terms
Spec
A written description of what to build, written before building it.
Testing
The cheapest way to know a change is safe: a check that runs without a human reading anything.
Handoff
Moving work from one session, or one agent, to another without losing the thread.
Agentic Workflow
A process where an agent does a meaningful part of the work, not just answers a question about it.
Human in the Loop
A person who reviews, approves, or corrects the agent's work at key points.
Want this working inside your team?
It starts with one conversation about your workflow.