ado-sprints-capacity
Skill5 starsChanged 5 months agoMITView on GitHub
Use when the user asks about sprint planning, iterations, team capacity, or wants to create or update iteration schedules. "what is the current sprint", "show team capacity for Sprint 12", "create a new iteration called Sprint 13", "set Alice's capacity to 6 hours per day", "how many days are left in the current sprint", "list all iterations in the release plan", "update the sprint end date", "who has remaining capacity this sprint"
In this repository10 other files it gives its agents.
- ado-contextSkill
- ado-pipelinesSkill
- ado-pm-reportingSkill
- ado-project-discoverySkill
- ado-pull-requestsSkill
- ado-repositoriesSkill
- ado-searchSkill
- ado-test-plansSkill
- ado-wikiSkill
- ado-work-itemsSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 39
Call work(project, team) to get the active iteration: name, start date, end date, total working days, and the team's committed work items.
- Very specific: line 47
Call work(project, team) — returns the current, past, and upcoming iterations.
- Very specific: line 94
When capacity is not yet set for a sprint, work returns zero for all members.
- Very specific: line 101
If activeProject is set, use it automatically as the project parameter — do not ask the user to re-specify it.
- Very specific: line 103
If no context is set and a project is required, invoke Workflow E of ado-context to resolve it (list projects, ask user to pick, then …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
ADO Sprints & Capacity
Manage Azure DevOps iterations (sprints), team capacity settings, and sprint planning boards. Read current sprint status and write capacity or iteration changes.
When to use
- User wants to see current and upcoming iterations for a team
- User wants to create a new iteration / sprint
- User wants to set or update team member capacity for a sprint
- User is doing sprint planning and needs capacity vs. committed work analysis
- User wants to move work items to a different iteration
MCP tools used
| Tool | Purpose |
work | Get sprint/iteration board and current work overview for a team |
work_capacity_write | Set or update daily capacity for a team member in a sprint |
work_iteration_write | Create or update an iteration (sprint) definition |
Workflow
Getting the current sprint overview
- Call
work(project, team)to get the active iteration: name, start date, end date, total working days, and the team's committed work items. - Derive capacity utilisation: committed story points vs. total available hours if capacity is set.
- Present the Sprint Overview table.
Listing iterations
- Call
work(project, team)— returns the current, past, and upcoming iterations. - Present as an Iterations table with state (active / past / future) and date ranges.
Creating a new iteration
- Extract: project, iteration name, start date, end date from the user request.
- Call
work_iteration_write(project, name, startDate, endDate). - Confirm creation and surface the option to assign work items to the new sprint.
Setting team capacity
- Identify: project, team, sprint name, team member name, and hours per day.
- Call
work_capacity_write(project, team, iterationId, memberId, hoursPerDay, daysOff). - Confirm the update with the new capacity value.
Output Format
Sprint Overview
| Field | Value |
| Sprint | Sprint 12 |
| Start | 2026-05-26 |
| End | 2026-06-08 |
| Working days | 10 |
| Team | Platform Core |
Team Capacity
| Member | Capacity (h/day) | Days off | Available (h) |
| Alice Martin | 6 | 0 | 60 |
| Bob Nguyen | 7 | 1 | 63 |
| Carlos Silva | 6 | 2 | 48 |
| Team total | — | — | 171 |
Iterations
| Iteration | State | Start | End |
| Sprint 11 | Past | 2026-05-12 | 2026-05-25 |
| Sprint 12 | Active | 2026-05-26 | 2026-06-08 |
| Sprint 13 | Future | 2026-06-09 | 2026-06-22 |
Notes
- Iteration IDs (GUIDs) are needed for
work_capacity_write; retrieve them fromwork. - When capacity is not yet set for a sprint,
workreturns zero for all members. Prompt the user to set capacity before doing a sprint commitment analysis. - Date format for
work_iteration_write: ISO 8601 (YYYY-MM-DD).
Active context
This skill respects the session context set by the ado-context skill.
- If
activeProjectis set, use it automatically as theprojectparameter — do not ask the user to re-specify it. - If no context is set and a project is required, invoke Workflow E of
ado-contextto resolve it (list projects, ask user to pick, then proceed).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.