Add support for Azure Devops with the skill 045-planning-azure-devops

[jabrena]

User Story: Add support for Azure Devops with the skill 045-planning-azure-devops

As a maintainer
I want to create a new skill 045-planning-azure-devops using ideas from 043-planning-github-issues and 044-planning-jira
So that maintainers can interact with Azure DevOps through the official Azure DevOps CLI and perform the same planning actions currently supported for GitHub and Jira workflows.

Acceptance Criteria

Feature: Interact with azure devops

@acceptance-test
Scenario: Interact with Azure DevOps work item URL
  Given the new skill `045-planning-azure-devops`
  When the user interacts with the skill by passing an Azure DevOps URL
  Then the skill uses the Azure DevOps CLI to perform the action requested by the user

Notes

• Review the current structure and behavior of 043-planning-github-issues and 044-planning-jira before implementing 045-planning-azure-devops.
• The new skill should mirror the existing planning-skill patterns where applicable, including CLI availability/configuration checks, tracker context handling, issue or work-item workflows, sanitized summaries for analysis, and secret-safe behavior.
• The skill should use Azure DevOps CLI capabilities for Azure DevOps work-item interactions, in the same spirit that 043 uses gh and 044 uses jira.

INVEST Validation

• Independent: The skill can be added as a new planning skill without requiring changes to existing GitHub or Jira skills beyond using them as implementation references.
• Negotiable: The exact Azure DevOps CLI commands and supported action set can be refined during implementation while preserving the goal of Azure DevOps planning support.
• Valuable: Maintainers gain a consistent workflow for Azure DevOps work items alongside the existing GitHub and Jira planning workflows.
• Estimable: Existing skills 043 and 044 provide concrete structure and behavioral patterns for sizing the new skill.
• Small: The scope is limited to adding one new planning skill and aligning it with established tracker-skill conventions.
• Testable: Completion can be verified by invoking the generated skill with an Azure DevOps URL and confirming that it routes the requested action through the Azure DevOps CLI pattern.

[wipheg]

hi @jabrena , i'd like to work on this issue. could you assign this to me?

[jabrena]

Hi @wipheg,

Someone else is working on it, but if you are interested on easy issues, I could propose other options if you like. :)
https://github.com/jabrena/cursor-rules-java/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22good%20first%20issue%22

Juan Antonio

[lealoureiro]

hey @jabrena!
As we discussed, I will pick up this one!