Parse Jira issues and score complexity across five dimensions.
npx skills add https://github.com/michaelalber/ai-toolkit --skill jira-review
Please help me install this Agent Skill. Skill: jira-review Source: https://github.com/michaelalber/ai-toolkit/tree/main/skills/jira-review Command: npx skills add https://github.com/michaelalber/ai-toolkit --skill jira-review
This Skill prevents wasted development effort by automatically reviewing Jira issues for clarity, completeness, and complexity before implementation begins, catching ambiguity early.
Use the jira-review skill to analyze the current Jira issue for implementation readiness.
High-intent search queries and answers about installing and using this skill.
To check Jira implementation readiness, you can automate the review of issue descriptions to parse acceptance criteria, identify missing information, and flag ambiguities before coding begins. This prevents wasted effort by ensuring alignment early.
Complexity scoring for Jira requirements is an automated assessment across five dimensions: scope, clarity, technical uncertainty, dependencies, and estimation confidence. This scoring identifies technical risks and evaluates whether an issue needs further clarification.
You can generate targeted clarifying questions for a Jira ticket by automatically parsing the issue description to identify ambiguities and missing information. This creates actionable questions for the product owner to ensure alignment before development starts.
Yes, you can automate the extraction of acceptance criteria and definition of done directly from Jira issue descriptions. The review process parses the text to evaluate completeness and assigns a readiness recommendation.
Yes, the Jira review process acts as an automated quality gate by assessing implementation readiness. It evaluates complexity and clarity to recommend whether an issue is ready to implement, needs clarification, or requires planning mode.
Automated Jira issue review relies on parsing text from issue descriptions, meaning it cannot assess unwritten technical contexts or unspoken team knowledge. It identifies ambiguities and missing information but cannot replace direct product owner communication for complex edge cases.
reVrostCreate Jira tasks with Prowler's standard format and acceptance criteria.
LaurentPRAT-DBAutomate Root Cause Analysis document drafting from Salesforce, JIRA, Slack, and email sources.
ConnectiveTCSPlan sprints with story estimation, capacity planning, and goal definition.
openshift-engAutomate creation of Jira stories with acceptance criteria.
