Convert a Jira Story Into Sub-Tasks With Owners and Estimates
Break a ready story into working steps without changing its scope.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Convert this Jira story into sub-tasks. The story (summary, description, acceptance criteria): [STORY_TEXT]. Team skills available (design, frontend, backend, QA, documentation): [TEAM_SKILLS]. Technical notes or constraints known so far: [TECHNICAL_NOTES]. The sprint length and the largest sub-task we accept: [SPRINT_AND_LIMIT]. Size scale: [SCALE]. Propose sub-tasks in the order they would be done, as a table with Sub-task (a summary starting with a verb), Description (one sentence), Skill, Size, Supports criterion and Depends on. Include testing and review as their own sub-tasks, and a documentation sub-task if the story changes behaviour users can see. No sub-task may be larger than the limit; split any that is. Check that every acceptance criterion is covered by at least one sub-task and list any sub-task that traces to no criterion, since it may be scope creep. Give the total size with the arithmetic and compare it with the story's estimate; if the total is much larger, say so and suggest whether the story is too big. Sub-tasks are working steps, not new features: mark anything unclear as a question. Wording should let a new team member pick up any sub-task. Sub-task issue types and fields depend on the project configuration [VERIFY].
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.