Skill: devops-validation
SkillCloud & infraUsar 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.
No other account needed.
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-statusor/pbi-decomposeon a new project
What Gets Validated
8 checks, in order — each returns PASS / WARN / FAIL:
| # | Check | What | FAIL if |
|---|---|---|---|
| 1 | Connectivity | PAT can reach org | HTTP != 200 |
| 2 | Project | Project name exists | Not found |
| 3 | Process | Template is Agile | Basic or CMMI |
| 4 | Types | Epic, Feature, US, Task, Bug | Any missing |
| 5 | States | New, Active, Resolved, Closed per type | Required state missing |
| 6 | Fields | StoryPoints, RemainingWork, etc. per type | Required field missing |
| 7 | Backlog | Hierarchy + bug behavior | — (WARN only) |
| 8 | Iterations | Sprints have dates | No 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:
- List each FAIL with its
remediationfield - Group by action type (process change, type addition, etc.)
- All changes require manual execution in Azure DevOps UI
- After PM applies changes → re-run
/devops-validateto confirm
Remediation Categories
| Category | Action Required | Where |
|---|---|---|
| Process template | Change to Agile | Organization Settings > Process |
| Missing types | Add via inherited process or migrate | Organization Settings > Process |
| Missing states | Customize via inherited process | Organization Settings > Process |
| Missing fields | Add to WIT layout | Organization Settings > Process > WIT |
| Bug behavior | Change to "as requirements" | Project Settings > Boards > Team config |
| No iterations | Create sprints with dates | Project 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
ahel recommends instead
Advanced
- Catalog kind
- skill
- Gateway key
devops-validation-gonzalezpazmonica- Source
- github.com/gonzalezpazmonica/savia