Azure DevOps PBI Skill

Status: Production Ready

Create, update, review, or close Azure work items from the current product scope. The skill routes by operation: a field edit remains a field edit; new PBIs follow the team's linked-task default; implementation and closeout preserve commitment, validation, merge, and release gates.

Setup and requirements

Use New User Setup and the skill-specific installer:

scripts/setup-azure-devops-pbi-skill.sh copilot /path/to/project-repo
scripts/setup-azure-devops-pbi-skill.sh codex
scripts/setup-azure-devops-pbi-skill.sh cursor /path/to/project-repo

Requires access to the resolved Azure project and Azure CLI/DevOps extension or another available authenticated transport. Use normal az login with the user's own account; a user-owned local PAT is fallback only. Follow setup's corporate CA guidance for TLS inspection failures; do not disable verification or borrow credentials.

The project profile holds contract defaults, not permission to redirect another product's work. A clear live parent and product context suffice within an authorized task. Ask when the parent/owner remains ambiguous or a new Feature expands scope.

Behavior

• Creation includes linked child tasks unless PBI-only/draft-only/no-task scope, access, or missing requirements prevents it. Planning applies only when creating/scoping tasks.
• Resolve implementation ownership separately from the PBI's PO; verify assignments and field conventions. Separate testing tasks depend on applicable scope and team pattern, with qualified current-capacity ownership.
• Verify Committed before execution or burn-down. Commitment requires recorded Scrum Master/authorized approver approval. Non-started backlog preparation can happen earlier.
• Close source-changing delivery only after required validation, pushed/merged non-draft PR, target verification, and applicable product/release gates. Analytics cannot waive those gates.
• The current team profile enables analytics for authorized write/execution workflows. Use safe metadata/counter tools; no telemetry posts for read-only review. Metadata failures remain nonblocking and reported.

Example prompts

• Create the PBI for this work under Feature 12345 and assign implementation tasks to me.
• Shorten only the acceptance criteria for PBI 12345.
• Review PBI 12345 without changing Azure.
• Finish PBI 12345 and verify the required delivery gates.

Expected output and validation

Return affected URLs/IDs, verified final state/fields, required evidence, and unresolved inputs. Report unsaved drafts on access failures and analytics status when applicable.

Use test scenarios for scoped dry runs; live tests require an approved real/test parent. Run npm run analytics:docs after metadata-reference changes; it validates examples against the shared parser without external credentials.

The detailed analytics contract remains in Agent Analytics Metadata Contract.