Paste your sprint goal. Get a quality score against 6 criteria — outcome vs deliverable, measurability, single-focus, beneficiary, length, vague language. Plus concrete fixes.
Tip: A good goal is one sentence the team can quote in standup. If you have to scroll to read it, it's too long.
SprintFlint pins the sprint goal to every issue and tracks goal-hit rate sprint over sprint. The goal stops being a meeting artefact.
Start FreeSix criteria, weighted: outcome focus (25), measurability (25), single-goal (20), names a beneficiary (15), reasonable length (10), no vague verbs (5). The first two are most decisive — a goal can pass length and tone checks while still being a deliverable in disguise.
Trust the criteria. The most common failure mode is "ship X" goals where X is a deliverable. If your goal looks like "build the dashboard" rather than "X% of users adopt the dashboard within 14 days", the validator will mark you down — and it's right to.
Without a measurable target, "did we hit the goal?" is a debate, not a fact. Half the value of a sprint goal is having a yes/no answer at retro. No number = no signal.
Rank them. The sprint goal is the *most important* one — the one you'd protect when something has to give. The others stay in the sprint plan as supporting outputs. Two equally-important priorities means neither will get the attention they need.
Yes — the validator scores *form*, not strategic correctness. A perfectly-formed goal that's pointed at the wrong outcome is still wrong. The validator is a sanity check on writing quality, not on what to optimise toward.
"Improve" is unmeasurable by itself. "Improve checkout" doesn't tell anyone whether you hit the goal. "Reduce checkout abandonment from 38% to 30%" does. The vague-verb check forces specificity.
Try the Sprint Goal Generator (5 templates per sprint type) or read 12 real-team examples.