Auditor and reporting
Who this is for
This block is for PMO leads and senior management:
- PMO — project delivery-quality checks and fact-based status verification, not verbal optimism.
- Senior management — an unbiased view of the project and portfolio, financial snapshot checks, and a legal / contractual risk overview grounded in recorded sources.
The Auditor is the skill set that replaces “we’re basically on plan” with hard data and source links.
Core competencies
The auditor looks at the project from the outside:
- Objective status reporting: progress from closed work and recorded effort.
- Variance analysis: baseline plan vs actual movement.
- Delivery-quality review (methodology health): whether the current phase has the right artefacts and decisions (charter, scope, RAID, sprint health, close-out readiness) — and what to do about gaps.
- Silent problems: issues formally In Progress but idle for days.
How to use
There is no separate role button: ask for a report or a quality review — the agent applies /report, /status-delta, or /quality.
Example prompts:
- “Prepare the weekly stakeholder status: what shipped, which risks appeared, and the current release-date forecast.”
- “Run a delivery-quality review for the current phase: which artefacts exist, which are missing, and what is the action plan?”
- “Compare actual progress on the Integration epic with the original plan. How far are we off the schedule?”
Skills used
- Status reporting (
/report): progress facts with sources; with a template — a presentation (.pptx). - Report formatting (
/report-format): structure for a given stakeholder. - Variance analysis (
/status-delta): period snapshot comparison. - Delivery quality (
/quality): phase methodology evidence checklist (initiate → close), Present / Partial / Missing table, and gap action plan. Not a work inventory (/status-snapshot) and not the stakeholder letter (/report).
Report directly in the slides
With a presentation template (.pptx), the agent fills the new period: texts, figures, and tables, keeping design and branding. You review and send.
Working principles
- A “90% done” status is not accepted without supporting artefacts in the tracker or materials.
- Every conclusion links to an issue or document.
- Metrics are standardized so projects can be compared.
That is how PMO prepares reporting meetings, and senior management gets a verifiable picture without status polishing.
