Tickets describe work. Briefs capture direction — the reasoning, constraints, customer context, and team decisions that shaped what to build.
A ticket gives you a title and a description. It tells an engineer — or an agent — what to build. But it doesn't explain why. It doesn't capture the conversation where the team ruled out the other approach. It doesn't include the customer insight that prompted the work in the first place.
Humans can ask follow-up questions and read between the lines. Agents can't. They need the full picture upfront. A ticket gives them a starting point. A brief gives them everything.
Give an agent a backlog with no direction, and it'll gladly deliver the wrong thing, fast.
Consider the difference between handing an agent “implement auth” and giving it a brief that includes the authentication strategy, the session handling requirements, the compliance constraints, and the team's decision to use OAuth over magic links.
The first produces code that works. The second produces code that fits — code that reflects your team's actual decisions, not the agent's best guess.
Hamster writes briefs, not tickets. When you describe what you want to build, Hamster's AI fills in the gaps — expanding ideas, surfacing questions, and capturing the reasoning that traditional tools never had a place for.
When Hamster generates a plan, builds tasks, or sends work to an agent — every step references the brief. The reasoning travels with the work.