Skip to content
Beta Multi-model support (OpenAI, Gemini, and more) launching soon.
RBA RBA Skills

client-status-reporter

v0.1.0 ExperimentalNo security review by Dakota Smith

Install

Pick the surface you use. Plugins run inside Claude Code, which is available in the terminal CLI, the desktop app on Mac and Windows, the web app at claude.ai/code, and the VS Code and JetBrains extensions. The slash commands are identical on every surface.

From inside any Claude Code session — terminal, desktop app, web app, or IDE extension:

  1. Add the RBA Skills marketplace (only needed once per machine):

    /plugin marketplace add rbaconsulting/rba-skills-plugin

  2. Install client-status-reporter:

    /plugin install client-status-reporter@rba-ai-hub

  3. Activate it without restarting:

    /reload-plugins

Overview

Client Status Reporter

Multi-audience project status reporting for RBA delivery teams. Pulls live sprint, work-item, pipeline, and timesheet data from Azure DevOps and Jira via MCP, then drafts polished reports tailored to three distinct audiences: executive sponsors, client stakeholders, and internal engineering teams.

No more copy-pasting from Azure Boards or screenshot-driven decks. Run a single command and get a ready-to-send status update that reflects what actually happened this week.

What's in this bundle

Artifact Purpose
status-data-pull skill Queries Azure DevOps / Jira MCP servers; normalises sprint velocity, work-item state, pipeline health, and timesheet burn into a structured data snapshot
status-report-draft skill Takes a data snapshot and drafts multi-audience status reports (executive, client, engineering) — switchable by argument
status-distribute skill Formats the drafted report for the target channel: email body, Teams adaptive card, Confluence page, or markdown file
status-report-reviewer agent Reads a drafted report and flags inaccuracies, missing RAG decisions, placeholder text, and tone mismatches before it goes out
/status-report command Guided entry point — runs the full pipeline or individual skills with a single slash command
.mcp.json Pre-configured MCP server entries for azure-devops (Microsoft GA server) and mcp-atlassian (Atlassian Cloud remote MCP)

When to use

  • Weekly / bi-weekly status cadence — automate the Friday status email
  • Sprint review prep — pull sprint data before the ceremony and generate the engineering summary
  • Executive steering committee — produce a one-page RAG summary with decisions and risks
  • Client portal / Confluence — push formatted status directly to a client-facing Confluence page
  • Portfolio reporting — run across multiple projects and aggregate into a portfolio view

Audience adapters

The reporting is platform-agnostic with swappable audience adapters:

Adapter Report depth Primary channel
executive 1-page RAG summary, budget burn, top 3 risks, decisions needed Email / Teams card
client Sprint highlights, milestone tracker, next-period preview, open items Email / Confluence
engineering Full sprint breakdown, velocity chart, PR/pipeline status, blocked items Teams channel / Markdown

Supported data sources

Primary (via MCP):

  • Azure DevOps — work items, sprints/iterations, pipeline runs, pull requests, wikis (uses microsoft/azure-devops-mcp)
  • Jira Cloud — issues, sprints, worklogs, JQL queries (uses Atlassian Remote MCP Server)

Timesheet adapters (via REST):

  • Tempo Timesheets (Jira-native)
  • Azure DevOps time-tracking custom fields
  • Harvest (REST API)

Installation

claude plugin install client-status-reporter@rba-ai-hub

Pre-requisites:

  1. Azure DevOps Personal Access Token (or Entra ID / OIDC) — set AZURE_DEVOPS_ORG and AZURE_DEVOPS_PAT environment variables.
  2. Atlassian API token — set JIRA_BASE_URL, JIRA_EMAIL, and JIRA_API_TOKEN for Jira-connected projects.
  3. Review .mcp.json in this bundle and update the orgUrl and baseUrl values for your project.

Quick start

/status-report                          # interactive guided mode
/status-report pull                     # pull latest data snapshot only
/status-report draft --audience client  # draft client report from latest snapshot
/status-report review status-draft.md  # run reviewer agent on a draft
/status-report send --channel teams    # format and post to Teams

RBA context

Designed for RBA's delivery model: fixed-price and T&M engagements across Sitecore XM Cloud, Umbraco 13, Optimizely CMS, composable Next.js/Astro frontends, and Azure cloud infrastructure. Budget burn, milestone RAG, and risk language reflect RBA's standard SOW structure.

Bundled artifacts

Skills

  • status-data-pull — Queries Azure DevOps and/or Jira via MCP to pull sprint progress, work-item state, pipeline health, PR throughput, and timesheet burn into a normalised JSON snapshot file ready for status-report-draft. Use at the start of every reporting cycle.
  • status-distribute — Formats a drafted status report markdown file for the target distribution channel — email body, Microsoft Teams adaptive card, Confluence page, or plain markdown — and outputs the ready-to-send payload. Use after status-report-draft produces a report.
  • status-report-draft — Reads a status snapshot (from status-data-pull) and drafts a polished status report for the specified audience — executive, client, or engineering. Handles RAG ratings, milestone tables, risk narratives, and next-period previews. Always produces report as a markdown file ready for status-distribute.

Agents

  • status-report-reviewer — Reviews a drafted status report (from status-report-draft) for factual accuracy against the source snapshot, completeness for the stated audience, placeholder text, RAG consistency, and tone appropriateness before distribution. Invoke after status-report-draft and before status-distribute.

MCP Servers

  • azure-devops — Microsoft Azure DevOps MCP Server (GA) — exposes work items, sprints/iterations, pipeline runs, pull requests, test plans, repositories, and wiki tools. Set AZURE_DEVOPS_ORG (e.g. 'rbaconsulting') and AZURE_DEVOPS_PAT in your environment before use. Domains: work-items, work, pipelines, repositories, test-plans, wiki.
  • mcp-atlassian — mcp-atlassian (sooperset/mcp-atlassian) — open-source MCP server for Jira Cloud and Confluence Cloud. Exposes issue search via JQL, worklog retrieval, sprint queries, and Confluence page read/write. Set JIRA_URL, JIRA_USERNAME, JIRA_API_TOKEN in your environment. Optional CONFLUENCE_* vars enable Confluence page publishing.

Slash Commands

  • /status-report — Guided entry point for the Client Status Reporter pipeline — pull data, draft reports, review, and distribute in one command. Runs individual stages or the full end-to-end pipeline.
Technical details
Homepage
https://rba-skills.tylerschroeder.net/plugins/client-status-reporter/
License
MIT
Maturity
experimental
Security review
No security review
Owners
  • delivery
  • project-management
Platforms
azure-devops
Disciplines
project-management, delivery
Lifecycle
communicate
Tags
  • status-report
  • jira
  • reporting
  • stakeholder-communication
  • sprint-report
  • timesheets
  • multi-audience
  • client-delivery
Last updated
by Tyler Schroeder
Source
plugins/client-status-reporter/

Edit this plugin's README on GitHub — opens GitHub's web editor. No git knowledge needed.