Dextre PM Agent
In development · capabilities below are planned, not yet live
A project management assistant inside Dextre that a project manager calls up with a plain-language prompt. It reads live Azure DevOps data, drafts the document or the change, and waits. Nothing is written, pushed or sent until the project manager approves it.
How a project manager uses it
The same four steps apply to every capability. The order is fixed, and the last step is always the project manager's decision.
Prompt
The project manager describes the project or the task in plain language and supplies the context. The agent does not infer it from SDLC pipeline runs.
Read
Where the task needs it, the agent reads live Azure DevOps data: backlog, sprint board, blocked items, pull requests and work item history.
Review and edit
The agent proposes a draft or a change. It opens in the Dextre app, where the project manager edits it in full.
Approve
Only on approval does the agent export, push to Azure DevOps or distribute. There are no autonomous changes to Azure DevOps.
The PM Agent is a separate app within Dextre. It sits outside the five SDLC agents and is not part of the pipeline sequence. Agent actions are recorded in an audit trail.
Six capabilities
Each one produces something a project manager would otherwise build by hand. Every output is a proposal until it is approved.
Start the project
Prompt only, no live Azure DevOps read
Project Charter
Prompt onlyA structured initiation document drafted from a description of the project.
Covers: Purpose and justification, SMART objectives, scope in and out, deliverables, assumptions and constraints, sponsor and stakeholders, high-level timeline, budget reference, PM authority statement.
PM controls: Reviews and edits section by section.
Output: Word (.docx) or PDF. Optionally a linked Azure DevOps wiki page, on approval.
RACI Matrix
Prompt onlyRoles mapped to named team members for each workstream or deliverable.
Covers: Responsible, Accountable, Consulted and Informed for every row, built from the team and roles the project manager names.
PM controls: Edits any cell, adds or removes rows and columns, renames workstreams.
Output: Word, PDF or CSV. Not pushed to Azure DevOps, because a RACI is a planning document.
Work Breakdown Structure
Writes to Azure DevOpsA project decomposed into phases, deliverables, work packages and tasks, shown as an editable tree.
Covers: The full hierarchy from the project scope and key deliverables in the prompt.
PM controls: Adds, removes, renames and reorders items, and maps each level to the Azure DevOps hierarchy before anything is pushed.
Output: Epics, Features and User Stories created in Azure DevOps, on approval only.
Run delivery
Reads live Azure DevOps data
Sprint Plan
Reads and writes Azure DevOpsA sprint plan built from the current backlog and the capacity the project manager states.
Covers: Sprint goal, prioritized stories that fit the velocity reference, story point estimates, acceptance criteria summary, capacity allocation, dependencies, blockers and risk items.
PM controls: Swaps stories in or out, changes assignments, edits the goal, confirms which sprint the plan applies to.
Output: On approval, stories are assigned to the sprint in Azure DevOps, sprint metadata is updated and carry-over items are marked.
Risk Register
Reads Azure DevOpsA register generated from the project brief, then refreshed from live sprint data whenever the project manager asks.
Covers: Technical, resource, scope, schedule and dependency risks, each with probability, impact, score, owner, response strategy and mitigation action.
PM controls: Edits rows. On a re-prompt, the agent reads signals such as blocked items, overdue tasks and scope-change pull requests and proposes new risks or status changes. The PM approves before anything is saved.
Output: Word or PDF. Optionally an Azure DevOps wiki page.
Report
Reads live Azure DevOps data
Status Report
Reads Azure DevOpsA weekly-style report drafted from live delivery data, reviewed by the project manager, then distributed.
Covers: Executive summary, overall Red, Amber or Green status, accomplishments, plan for the next period, risks and issues, and decisions required. Source data includes completed and in-progress stories, blocked items, burndown, and pull requests raised and merged.
PM controls: Edits the whole report. The agent proposes the RAG status and the project manager has the final say.
Output: On approval, posted to a pre-configured Teams channel and emailed to a pre-configured recipient list. A copy is saved to SharePoint in the project folder.
Inputs and outputs at a glance
| Capability | Reads live Azure DevOps | Edited in the app | Export |
|---|---|---|---|
| Project Charter | No | Section by section | .docx, PDF |
| RACI Matrix | No | Any cell, row or column | .docx, PDF, CSV |
| Work Breakdown Structure | No | Editable tree | Not specified |
| Sprint Plan | Yes, the backlog | Stories, assignments, goal | Not specified |
| Risk Register | Yes, on re-prompt | Editable table | .docx, PDF |
| Status Report | Yes | Full report | Teams, email, SharePoint copy |
Built-in limits
Approval on every action
Each proposed change waits for explicit sign-off from the project manager. No autonomous changes to Azure DevOps.
The PM sets the trigger
The agent runs when asked. It does not update the risk register between prompts, and status reports are on demand, not scheduled.
The PM decides the call
The agent proposes the Red, Amber or Green status from the data. The project manager confirms or overrides it before the report goes out.
Stands on its own
The agent works from the prompt and live Azure DevOps data. It has no automatic connection to SDLC pipeline runs.