Check a Jira Story Against INVEST and Definition of Ready
Review a drafted story and return a verdict plus a rewritten version.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Review this Jira story against the INVEST checklist and our definition of ready. Story text (summary, description, acceptance criteria): [STORY_TEXT]. Our definition of ready, if we have one: [DEFINITION_OF_READY]. Team size and sprint length: [TEAM_AND_SPRINT]. Score each INVEST letter from 1 to 5 (Independent, Negotiable, Valuable, Estimable, Small, Testable) with a quoted line as evidence. When a letter cannot be judged from the text, write 'cannot judge' and give the question that would settle it; do not reward long descriptions for being long, or give a 5 to anything dependent on a story not yet written. Then check each definition-of-ready item as met, partly met or missing; my definition is the final authority when it conflicts with the generic checklist, and say when that happens. List the three biggest problems in order of effect on delivery, such as a hidden dependency, an untestable criterion, or a story too large for one sprint. Return a table with Criterion, Score or status, Evidence and Fix, a verdict (ready, ready after small edits, or needs a refinement conversation), and a rewritten story that fixes what can be fixed from my text alone, staying close to the original wording and marking each change in square brackets. Put questions only the team can answer in a separate list, name any dependency on another team with the question to ask, and do not invent scope. End with a two-sentence coaching note on the one habit that would most improve the author's next story.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.
See an example result (fictional data)
Invented story: 'As an admin I want to manage users.' Scores: Independent 3, Negotiable 4, Valuable 3, Estimable 1 (scope unknown), Small 1, Testable 1. Evidence: 'manage' covers create, edit, delete, roles, which is at least four stories. Verdict: needs a refinement conversation. Rewrite: 'As an admin I want to deactivate a user, so that a leaver loses access immediately' with criteria: Given an active user, when I deactivate them, then they cannot sign in and their data is kept. Questions for the team: do we also need reactivation?
Illustrative only, made-up data. Your results will differ and must be reviewed.