omc-ado-sprint

OMC ADO Sprint

Perform a full Azure DevOps sprint planning cycle for the current project. Reads .omg/config.json for connection settings, queries iterations and team capacity, reviews the backlog, and helps assign work items to sprints.

When this skill is invoked, immediately execute the workflow below. Do not only restate or summarize these instructions back to the user.

Trigger Patterns

• "ado sprint"
• "sprint planning"
• "plan sprint"
• "manage iterations"
• "check capacity"
• "groom backlog"
• "assign to sprint"
• "omc-ado-sprint"

---

Step 1: Load Configuration

Read .omg/config.json:

node -e "const f=require('fs');try{process.stdout.write(f.readFileSync('.omg/config.json','utf8'))}catch{console.log('NOT_FOUND')}"

Extract from the ado key:

• org — full org URL (e.g. https://dev.azure.com/contoso)
• project — ADO project name
• team — team name (e.g. contoso Team)
• repo — repository name
• areaPath — area path filter (optional)
• iterationPath — current iteration path (optional)

If config is NOT_FOUND or missing the ado key: tell the user to run /oh-my-copilot:omc-ado-setup first and stop.

---

Step 2: List Current Iterations

Fetch all iterations assigned to the team to understand the sprint timeline.

MCP (preferred):

mcp__azure-devops__work_list_team_iterations
  → project: "{project}"
  → team: "{team}"

Also fetch all project-level iterations for reference:

mcp__azure-devops__work_list_iterations
  → project: "{project}"

az CLI fallback:

az boards iteration team list \
  --team "{team}" \
  --project "{project}" \
  --org "{org}" \
  -o json 2>&1

Present the iterations in a table:

### Current Iterations
| Name | Start Date | End Date | Status |
|------|-----------|----------|--------|
| Sprint 22 | 2026-03-01 | 2026-03-14 | current |
| Sprint 23 | 2026-03-15 | 2026-03-28 | future |

Identify the current iteration (today's date falls within its date range) and the next iteration for planning purposes.