Skill: devops-validation

SkillCloud & infra

Usar cuando se conecta un proyecto nuevo a Azure DevOps para validar su configuración Agile.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Skill: devops-validation skill

What this skill tells your AI

The instructions your AI receives, as published by gonzalezpazmonica/savia in .claude/skills/devops-validation/SKILL.md and read by ahel’s review.

Audits an Azure DevOps project to verify it matches pm-workspace's "ideal Agile" configuration. Generates a remediation plan for manual approval if mismatches are found.

Prerequisite: Read .opencode/skills/azure-devops-queries/SKILL.md first.


When to Invoke

  • PM connects a new project to pm-workspace (provides org URL, project, team, PAT)
  • PM runs /devops-validate --project {p} [--team {t}]
  • Before first /sprint-status or /pbi-decompose on a new project

What Gets Validated

8 checks, in order — each returns PASS / WARN / FAIL:

#CheckWhatFAIL if
1ConnectivityPAT can reach orgHTTP != 200
2ProjectProject name existsNot found
3ProcessTemplate is AgileBasic or CMMI
4TypesEpic, Feature, US, Task, BugAny missing
5StatesNew, Active, Resolved, Closed per typeRequired state missing
6FieldsStoryPoints, RemainingWork, etc. per typeRequired field missing
7BacklogHierarchy + bug behavior— (WARN only)
8IterationsSprints have datesNo iterations at all

Full field/state mapping: → references/ideal-agile-config.md


Running the Validation

scripts/validate-devops.sh \
  --project "ProjectName" \
  --team "ProjectName Team" \
  --output output/devops-validation.json

Returns JSON report to stdout and optionally to file.


Interpreting Results

All PASS → Project is ready for pm-workspace. Proceed with /sprint-status or /pbi-decompose.

Any WARN → Non-blocking issues. WIQL queries will work but some fields may return null or behavior may differ. List warnings to PM with remediation steps.

Any FAIL → Blocking issues. Generate remediation plan for PM approval:

  1. List each FAIL with its remediation field
  2. Group by action type (process change, type addition, etc.)
  3. All changes require manual execution in Azure DevOps UI
  4. After PM applies changes → re-run /devops-validate to confirm

Remediation Categories

CategoryAction RequiredWhere
Process templateChange to AgileOrganization Settings > Process
Missing typesAdd via inherited process or migrateOrganization Settings > Process
Missing statesCustomize via inherited processOrganization Settings > Process
Missing fieldsAdd to WIT layoutOrganization Settings > Process > WIT
Bug behaviorChange to "as requirements"Project Settings > Boards > Team config
No iterationsCreate sprints with datesProject Settings > Iterations

JSON Report Schema

{
  "project": "PM-Workspace",
  "team": "PM-Workspace Team",
  "org": "https://dev.azure.com/OrgName",
  "timestamp": "2026-02-28T10:00:00Z",
  "summary": { "total": 8, "pass": 6, "fail": 1, "warn": 1 },
  "checks": [
    {
      "check": "process",
      "status": "FAIL",
      "message": "Process Basic not compatible",
      "remediation": "Organization Settings > Process > Change to Agile"
    }
  ]
}

References

  • references/ideal-agile-config.md — Complete field/state/type mapping
  • ../azure-devops-queries/references/wiql-fields.md — WIQL field reference
  • Command: /devops-validate
  • Scripts: scripts/validate-devops.sh, scripts/validate-devops-checks.sh

Signals

GitHub stars
50
Forks
12
Last commit
Sep 2026
Advanced
Catalog kind
skill
Gateway key
devops-validation-gonzalezpazmonica
Source
github.com/gonzalezpazmonica/savia