azure-devops-backlog-refinement
/azure-devops-backlog-refinement
Prepare Azure Boards backlog refinement or grooming. Use to review stories, product backlog items, bugs, or requirements for clarity, acceptance criteria, dependencies, possible duplication, useful splits, and questions for the Product Owner and Developers.
- Author
- JeanMarcMbouma ↗
- Repository
- DevOpsAIPlugin ↗
- Licence
- MIT
- Last repository change
- 09.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Prepare Azure Boards backlog refinement or grooming. Use to review stories, product backlog items, bugs, or requirements for clarity, acceptance criteria, dependencies, possible duplication, useful splits, and questions for the Product Owner and Developers.
Original author description
Prepare Azure Boards backlog refinement or grooming. Use to review stories, product backlog items, bugs, or requirements for clarity, acceptance criteria, dependencies, possible duplication, useful splits, and questions for the Product Owner and Developers.
How it works
SKILL.md has no level-two headings · 24 lines, 352 words
SKILL.md preview
--- name: azure-devops-backlog-refinement description: Prepare Azure Boards backlog refinement or grooming. Use to review stories, product backlog items, bugs, or requirements for clarity, acceptance criteria, dependencies, possible duplication, useful splits, and questions for the Product Owner and Developers. --- # Backlog refinement Read [Azure Boards context](../azure-devops-workflow/references/boards-context.md) before fetching work. Follow its organization selection, process discovery, evidence, and edit rules. For synchronized Jira counterparts, use the [Jira bridge](../azure-devops-jira-bridge/SKILL.md) to resolve identity and edit ownership before refining or grouping items. Resolve the intended backlog level and item selection. For "the next ten items," establish the team's ordering field or use an ordering supplied by the user. Follow parent links when needed to understand the product outcome. For each selected item: 1. Identify the intended beneficiary, outcome, scope, and business context. Preserve the intent of bug reports and requirements when a user-story format would lose information. 2. Review the description and actual acceptance-criteria field. Separate missing information from unclear or contradictory information. Treat the team's readiness checklist as guidance and record questions where no checklist exists. 3. Draft observable acceptance criteria grounded in the supplied requirements. Include relevant failure cases suggested by those requirements. Label assumptions and proposed behavior for confirmation. When the supplied behavior is too sparse, ask targeted questions and leave replacement criteria pending. 4. Suggest smaller slices when the item spans several independent outcomes or unresolved decisions. Describe the value and acceptance criteria of each proposed slice and retain parent traceability. 5. Read the linked dependencies and note decisions needed before planning. Flag possible duplicates with links and the reason for similarity. Assess duplication only within the inspected scope. 6. Prepare sizing questions for the Developers. Preserve existing estimates and flag their uncertainty when appropriate. Ask the Product Owner to confirm ordering and trade-offs. Return a refinement worksheet with item links, observed gaps, proposed improvements or slices, dependencies, and open questions. For each proposed change, show the existing text or value and the draft replacement. Include the scope reviewed and evidence limitations. Summarize decisions needed for the refinement session. Keep drafts in the response until the user requests supported edits. When asked to apply a proposal, apply only the requested changes and report the resulting work item links and revisions. Example requests include "Prepare the next ten backlog items for grooming" and "Suggest acceptance criteria and smaller slices for these stories."
Versions
The database has no other skills named azure-devops-backlog-refinement.
Database snapshot: 13.11.2026 · package version 1bfb984f98c8 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100audit-backlog-ado
Audits the Azure DevOps product backlog for hygiene, story quality, and refinement readiness — identifying items that are too large, missing acceptance criteria, stale, unestimated, or out of priority order. Use when a Scrum Master or Product Owner says things like "audit the… - 100product-specification
Turn ambiguous product ideas into clear product requirements, user stories, acceptance criteria, scope boundaries, and delivery plans. Use for feature discovery, MVP definition, stakeholder alignment, backlog refinement, and product change proposals. - 90scrum-event-backlog-refinement
Transform PBIs into ready status for AI execution. Use when refining backlog items, splitting stories, or ensuring Definition of Ready. - 90backlog-execute
Mutating backlog execution for Azure DevOps, GitHub, and Jira. Use to create one item or apply a reviewed handoff to a confirmed tracker. - 100boards-backlog-summary
Get the team's Requirements-level backlog (Product Backlog Items and Bugs) filtered to Active items assigned to the current user. Shows parent/child hierarchy and sorts by priority. Use this skill when the user wants to see their backlog items, sprint assignments, or work they own on a team board. - 100backlog-grooming-assistant
Execute backlog grooming assistant operations. Auto-activating skill for Enterprise Workflows. Triggers on: backlog grooming assistant, backlog grooming assistant Part of the Enterprise Workflows skill category. Use when working with backlog grooming assistant functionality.…