Why a Sprint Goal isn't a task list
A Sprint Goal is the single objective the sprint serves - the thing that gives an otherwise arbitrary batch of tickets a reason to be in the same sprint together. It's not a summary of what's in the sprint; it's the answer to "why are we doing this sprint" that the team can use to make tradeoffs when something unexpected comes up mid-sprint. A goal that just lists work ("finish tickets X, Y, and Z") fails that test - dropping any one of the tickets wouldn't change the goal, which means it isn't really providing coherence.
How the generator works
No AI, no randomness - the sentence above is built from a fixed template per outcome type, filled in with what you type. Five outcome shapes cover most real sprints: shipping something new, improving something existing, fixing a problem, de-risking an unknown, or reducing a cost. The "so that" field is optional but worth filling in - a goal with a stated reason is easier for the team to reason about mid-sprint than a goal with none.
Using the result
Treat the generated sentence as a first draft, not a final answer. Read it back and ask: if we dropped this goal, would anything about this sprint actually change? If the honest answer is no, the focus is probably too broad or too task-shaped - narrow it until the answer is yes.