backlog-grooming

Review Jira stories for completeness, acceptance criteria, and dependencies.

1|1|Updated Feb 24, 2026
One-click install
npx skills add https://github.com/nroze22/TalosixSkills --skill backlog-grooming-nroze22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backlog-grooming
Source: https://github.com/nroze22/TalosixSkills/tree/main/.claude/skills/backlog-grooming
Command: npx skills add https://github.com/nroze22/TalosixSkills --skill backlog-grooming-nroze22

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires mcp__claude_ai_Atlassian__searchJiraIssuesUsingJql, mcp__claude_ai_Atlassian__getJiraIssue, mcp__claude_ai_Atlassian__editJiraIssue, mcp__claude_ai_Atlassian__addCommentToJiraIssue, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of backlog refinement, ensuring that user stories are well-defined, complete, and ready for development, thereby preventing delays and misunderstandings during sprint planning.

Core Features & Use Cases

  • Story Completeness Check: Validates stories against a comprehensive checklist, including user story format, acceptance criteria, and EDC-specific considerations.
  • Dependency Identification: Helps uncover hidden dependencies between stories and with external systems.
  • Acceptance Criteria Generation: Assists in creating clear, testable acceptance criteria.
  • Use Case: A Product Manager can use this skill to quickly assess a batch of new user stories, identify gaps in their descriptions or acceptance criteria, and get actionable recommendations for improvement before the next sprint planning meeting.

Quick Start

Use the backlog-grooming skill to review Jira tickets in the 'TALOSIX' project that are in the 'To Do' status and do not have the 'groomed' label.

Frequently Asked Questions about backlog-grooming

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I refine Jira user stories for sprint planning?

You can refine Jira user stories by pulling tickets in 'To Do' status, checking them against a completeness checklist, generating acceptance criteria, and adding the 'groomed' label once they meet sprint readiness standards.

What does backlog grooming check for in a user story?

Backlog grooming validates user story format, verifies acceptance criteria are present and testable, and uncovers hidden dependencies between stories or external systems to prevent sprint delays.

Can I automatically update Jira tickets during backlog refinement?

Yes, the backlog refinement process integrates directly with Jira to pull ticket information, edit issues to add missing acceptance criteria, and add comments with actionable improvement recommendations.

How do I write testable acceptance criteria for user stories?

Writing testable acceptance criteria involves generating clear, verifiable conditions that define story completion. The refinement process assists in creating these criteria while validating the overall story against EDC-specific considerations.

When do I need to identify dependencies during backlog grooming?

Dependency identification is needed during backlog grooming when stories have hidden relationships with other tickets or external systems, which if left undiscovered will cause delays and misunderstandings during sprint planning.