/code @devintern/pm DevIntern + Azure DevOps
Keep Azure Boards as your source of truth. @devintern/pm files well-specified work items, and @devintern/code implements them end-to-end with PRs and state transitions.
How it works
What DevIntern does with Azure DevOps
Each product path keeps Azure DevOps as the handoff surface. No rip-and-replace, no new dashboard.
/pm File work items in Azure DevOps
- 1 Set TASK_TRACKER=azure-devops with org, project, and PAT.
- 2 Run the interactive flow with your source material.
- 3 Review the draft and create the work item in your project.
/code Implement work items end-to-end
- 1 Run devintern against a work item ID, URL, or a WIQL batch query.
- 2 Agent fetches the description, comments, attachments, and linked parent or child items.
- 3 Creates a branch, implements, self-reviews, opens a PR, and comments back on the work item.
Capabilities
Built for real Azure DevOps workflows
Azure DevOps REST API for work item creation and implementation
Issue type selection in the interactive flow
HTML descriptions converted to markdown for your agent
State transitions via workflow state names in settings.json
WIQL batch runs for draining a filtered backlog
Story Points field updates in estimation mode
A single run
From Azure DevOps ticket to reviewed pull request
A single run takes a work item from ID to reviewed pull request, moving it through the states of your process template along the way.
- 1
Fetch the work item
DevIntern pulls the work item over the Azure DevOps REST API. The HTML description is converted to markdown for your agent, and tags, attachments, comments, and linked parent, child, and related items come along as context.
- 2
Feasibility gate
The agent evaluates whether the work item, seen with its linked parent and child items, can be implemented as specified. If not, it posts an assessment with the blocking questions rather than shipping a guess.
- 3
State moves to Active
If the item passes the gate, DevIntern transitions it using the state names you configure per project in settings.json, matching your process template (New, Active, Resolved in Agile, for example).
- 4
Implement and self-review
Implementation happens on a feature branch with the full work item hierarchy as context. The agent then reviews its own diff and fixes issues before the pull request goes up.
- 5
Deliver back to Azure Boards
With --create-pr, DevIntern opens a pull request, moves the item to your review state, and posts an implementation summary comment. Incomplete runs return the item to your starting state with an explanation.
What gets written back to Azure DevOps
Comments are written in markdown and converted to HTML before posting, so they render natively in Azure Boards. Use --skip-comments to run without comments or state transitions.
Feasibility check
Assessment comment with the questions blocking implementation
Successful implementation
Implementation summary comment with a link to the pull request
Incomplete run or max turns
Incomplete-run comment explaining what remains
Estimation run
Estimate written to the Story Points field, plus a comment with the reasoning
Batch runs
Work through Azure DevOps in batches
Batch selection uses WIQL, the query language behind Azure Boards queries, scoped to your configured project. The first 100 matching work items are processed in sequence.
Single work item, PR included
$ devintern 4211 --create-pr Drain everything in New
$ devintern --query "SELECT [System.Id] FROM WorkItems WHERE [System.State] = 'New'" --create-pr Everything tagged bug
$ devintern --query "SELECT [System.Id] FROM WorkItems WHERE [System.Tags] CONTAINS 'bug'" --create-pr AI story point estimation
$ devintern 4211 --estimate Writes to Microsoft.VSTS.Scheduling.StoryPoints by default; set storyPointsField for templates that use Effort.
Azure DevOps specifics at a glance
API
Azure DevOps REST API with a Personal Access Token
Query language
WIQL via --query, scoped to your project
Descriptions
HTML converted to markdown for the agent; comments converted back to HTML when posting
Status updates
State transitions matching your process template, configured per project in settings.json
Estimation
Story Points field (Agile default); configurable for Scrum's Effort field
Context
Parent, child, and related work item links included in the agent context
Get connected
Setup guides and configuration
Credentials stay in project-local .env files. DevIntern runs on your machine or server, not a shared implementation cloud.
FAQ
Common questions about Azure DevOps
Does @devintern/code implement Azure DevOps work items?
Yes. Set TASK_TRACKER=azure-devops, then run devintern against a work item ID or URL. It implements the change, opens a PR, moves the item through your workflow states, and posts summary comments. Batch selection works with WIQL via --query.
What permissions does the PAT need?
A personal access token with Work Items (read and write) scope for the target organization and project.
Which process templates are supported?
Any template works because state names are configured, not assumed. Match the states of your work item types in settings.json (New, Active, Resolved for Agile; other templates differ). For estimation, Scrum templates that use Effort instead of Story Points set storyPointsField per project.
What happens when a state transition fails?
DevIntern logs a warning and continues the run. State names differ per process template and work item type, so check the states available for that type in your project settings and match them exactly.
Try DevIntern with Azure DevOps
Connect Azure DevOps, run your first workflow, and keep the trackers, repos, and reviewers your team already trusts.
Free for interactive use · FSL source-available · BYO model keys