Skill: sprint-management
SkillDev toolsUse when querying sprint status, updating items, or generating the summary.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Skill: sprint-management skill
What this skill tells your AI
The instructions your AI receives, as published by gonzalezpazmonica/savia in .claude/skills/sprint-management/SKILL.md and read by ahel’s review.
Flujo completo de gestión de sprints: obtener estado, listar items, calcular progreso y generar resúmenes.
Prerequisito: Leer primero .opencode/skills/azure-devops-queries/SKILL.md
Constantes de esta skill
PROJECT_NAME="${AZURE_DEVOPS_DEFAULT_PROJECT}"
TEAM_NAME="${AZURE_DEVOPS_DEFAULT_TEAM}"
ORG_URL="${AZURE_DEVOPS_ORG_URL}"
SPRINT_DURATION_WEEKS=2 # ajustar si difiere
VELOCITY_SPRINTS=5 # sprints para media de velocity
Flujo 1 — Obtener el Sprint Actual
az devops configure --defaults organization=$ORG_URL project=$PROJECT_NAME
az boards iteration team list \
--project "$PROJECT_NAME" \
--team "$TEAM_NAME" \
--timeframe current \
--output json > /tmp/current-sprint.json
# Extraer: id, name, startDate, finishDate, iterationPath
Calcular días restantes:
FINISH=$(jq -r '.value[0].attributes.finishDate' /tmp/current-sprint.json | cut -c1-10)
DAYS_LEFT=$(( ($(date -d "$FINISH" +%s) - $(date +%s)) / 86400 ))
Flujo 2 — Obtener Work Items del Sprint
Ejecutar WIQL para obtener IDs de items:
WIQL='{"query": "SELECT [System.Id],[System.Title],[System.State],[System.AssignedTo],[System.WorkItemType],[Microsoft.VSTS.Scheduling.CompletedWork],[Microsoft.VSTS.Scheduling.RemainingWork],[Microsoft.VSTS.Scheduling.StoryPoints] FROM WorkItems WHERE [System.IterationPath] UNDER @CurrentIteration AND [System.TeamProject] = @Project ORDER BY [System.AssignedTo] ASC"}'
# Ejecutar curl y guardar en /tmp/sprint-ids.json
Flujo 3 — Calcular Progreso del Sprint
Detalle: @references/progress-metrics.md
Métricas a calcular:
- Story Points planificados vs completados
- RemainingWork total del equipo
- Distribución por estado
- Distribución por persona
Flujo 4 — Velocity y Tendencia
# Obtener últimos N sprints (past)
az boards iteration team list --project "$PROJECT_NAME" --team "$TEAM_NAME" \
--output json | jq '.value[] | select(.attributes.timeFrame == "past")'
# Para cada sprint: ejecutar query de SP completados
# Media = sum(SP_por_sprint) / num_sprints
Flujo 5 — Generar Resumen de Sprint
Detalle: @references/sprint-summary-template.md
Estructura: Período | Progreso | Por Persona | Alertas
Guardar Snapshot del Sprint
DATE=$(date +%Y%m%d)
SPRINT_DIR="projects/$PROJECT_NAME/sprints/$SPRINT_NAME"
mkdir -p "$SPRINT_DIR/snapshots"
cp /tmp/sprint-items.json "$SPRINT_DIR/snapshots/$DATE-items.json"
Errores Frecuentes
| Situación | Solución |
|---|---|
Sprint vacío (timeframe=current) | Configurar sprint en Team Settings |
| Items sin StoryPoints | Marcar ⚠️, no afectar denominador |
| RemainingWork=null | Tratar como 0, notificar |
| > 200 items | Usar paginación WIQL |
Referencias
references/progress-metrics.md— Métricas de progresoreferences/sprint-summary-template.md— Plantilla resumen- Azure DevOps Queries:
../azure-devops-queries/SKILL.md - Comandos:
/sprint-status,/sprint-plan,/sprint-review
Signals
- GitHub stars
- 50
- Forks
- 12
- Last commit
- Sep 2026
ahel recommends instead
Advanced
- Catalog kind
- skill
- Gateway key
sprint-management-gonzalezpazmonica- Source
- github.com/gonzalezpazmonica/savia