Loading WorkLenz...
Check every user story against INVEST criteria before it enters your sprint. Analyzes story text for vague words, dependencies, and testability.
Quality-Checked Stories for Every Sprint
Stop discovering story problems during sprint planning. This tool analyzes every user story against the INVEST criteria, flags vague language and hidden dependencies, scores your acceptance criteria, and gives you specific rewrite suggestions — all in your browser, no account needed.
Evaluates all six INVEST criteria — Independent, Negotiable, Valuable, Estimable, Small, Testable — with pass/partial/fail status and specific suggestions for each
Scans your story text for vague adjectives, dependency language, prescriptive phrasing, and conjunction patterns that signal stories are too large
Checks if acceptance criteria follow Given/When/Then structure and flags untestable or ambiguous criteria
Produces an overall quality rating — Poor, Fair, Good, or Excellent — so you know at a glance whether a story is sprint-ready
Automatically saves your last 10 checked stories so you can review past analyses and track improvement over time
Exports the full INVEST analysis as formatted Markdown — ready to paste into any project management tool or team documentation
Pro Tip
This tool runs entirely in your browser. Nothing is sent to any server. Your stories and analysis stay private on your machine.
Pro Tip
Check every story before sprint planning. Stories that score Good or Excellent lead to fewer blockers and more predictable sprint delivery.
Free to use - No account required - No credit card
Everything you need to know about checking user story quality with INVEST criteria
INVEST is a widely-used framework for evaluating user story quality. Each letter stands for a criterion: Independent (the story can be developed on its own without blocking dependencies), Negotiable (the details are open to discussion between the team and product owner, not a rigid contract), Valuable (the story delivers clear value to the end user or business), Estimable (the team has enough information to estimate the effort required), Small (the story fits within a single sprint and is not an epic that needs splitting), and Testable (you can write clear acceptance criteria that verify the story is done). A story that passes all six criteria is far more likely to be completed successfully within a sprint.
The tool scans your story text using pattern matching — no AI or external API calls. It checks for: vague words like 'easy', 'simple', 'fast', 'intuitive' that make stories unestimable; dependency language like 'requires', 'depends on', 'blocked by' that violate the Independent criterion; prescriptive phrasing like 'must use' or 'implemented in' that violate the Negotiable criterion; conjunctions like 'and', 'also', 'as well as' that often signal a story is trying to do too much; and missing 'so that' clauses that indicate the value proposition is unclear. Each finding is mapped to the specific INVEST criterion it affects.
Each of the six INVEST criteria is rated as Pass, Partial, or Fail. A Pass counts as 1 point, Partial as 0.5, and Fail as 0. The total determines the quality badge: Excellent (6/6), Good (4–5.5/6), Fair (2–3.5/6), or Poor (0–1.5/6). The score is displayed prominently so you can quickly decide whether a story needs rework before it enters your sprint backlog.
The tool checks whether your acceptance criteria follow a structured format — specifically looking for Given/When/Then patterns or numbered lists with specific, measurable outcomes. It also scans for vague language within the criteria themselves. Well-structured acceptance criteria make stories Testable (the T in INVEST) and help developers know exactly when a story is complete, reducing ambiguity and rework during the sprint.
Yes. The tool generates a complete Markdown-formatted report that includes the quality badge, per-criterion analysis with status and suggestions, flagged words found in the story text, and acceptance criteria quality assessment. You can copy this report and paste it into any project management tool, team wiki, or documentation system.
Absolutely. This tool runs entirely in your browser. All data — your stories, acceptance criteria, analysis results, and history — is stored only in your browser's localStorage. Nothing is sent to any server, and no account or registration is required. Your stories never leave your machine.
The best time to use this tool is during backlog refinement or sprint planning — before stories are committed to a sprint. Running each story through the quality checker catches issues early: stories that are too large get split, vague stories get clarified, and missing acceptance criteria get written. Teams that check story quality before sprint planning consistently report fewer mid-sprint blockers and more predictable delivery.