omc-ado-sprint

Plan Azure DevOps sprints and assign work items to iterations.

5|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/RobinNorberg/oh-my-copilot --skill omc-ado-sprint
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: omc-ado-sprint
Source: https://github.com/RobinNorberg/oh-my-copilot/tree/main/skills/omc-ado-sprint
Command: npx skills add https://github.com/RobinNorberg/oh-my-copilot --skill omc-ado-sprint

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating Azure DevOps sprint planning, capacity management, backlog grooming, and work-item assignments across iterations is error-prone and time-consuming. This skill automates an end-to-end sprint cycle for the current project by reading the .omcp/config.json, querying iterations and capacity, reviewing backlog, and assigning work items to the appropriate sprint, reducing manual overhead.

Core Features & Use Cases

  • End-to-end sprint planning: Loads configuration, lists iterations, checks capacity, reviews backlog, and assigns items to sprints.
  • Capacity-aware backlog alignment: Evaluates team capacity to propose achievable sprint scopes and mitigate over-commitment.
  • Iteration creation and assignment: Creates new iterations when needed and assigns them to the correct team, streamlining rollout for new sprints.
  • Use Case: A team wants to plan the next sprint cycle for a project with multiple backlogs and a fluctuating capacity; this skill generates a workable sprint plan and applies it.

Quick Start

Execute a full sprint planning cycle for the current project by loading your ADO config and running the omc-ado-sprint workflow.

Frequently Asked Questions about omc-ado-sprint

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

FAQPage Schema
How do I automate Azure DevOps sprint planning and backlog assignment?

Azure DevOps sprint planning is automated by loading project configuration, querying iterations, checking capacity, reviewing backlog, and assigning work items to sprints. It formats results in human-friendly tables for step-by-step execution.

Can I check team capacity before assigning work items to an iteration?

Yes, you can check team capacity before assigning work items. The skill evaluates team capacity to propose achievable sprint scopes and mitigate over-commitment during the iteration planning cycle.

Does this sprint planning tool require az CLI or MCP tools to function?

The skill relies on MCP tools and az CLI fallbacks to fetch data and apply updates within Azure DevOps. These tools enable loading configuration, querying iterations, and assigning work items to sprints.

How do I create new iterations in Azure DevOps for sprint planning?

You can create new iterations and assign them to the correct team during sprint planning. This streamlines rollout for new sprints by integrating iteration creation directly into the backlog assignment workflow.

What is the best way to align backlog grooming with fluctuating team capacity in Azure DevOps?

Capacity-aware backlog alignment is the best way to handle fluctuating team capacity. This approach evaluates team capacity to propose achievable sprint scopes and mitigates over-commitment risks during sprint planning.

Why should I not manually coordinate work-item assignments across multiple Azure DevOps backlogs?

Manually coordinating work-item assignments across multiple backlogs is error-prone and time-consuming. Automating the end-to-end sprint cycle reads configuration, checks capacity, and assigns items accurately to reduce manual overhead.