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

meeting-to-action

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 meeting-to-action:

    /plugin install meeting-to-action@rba-ai-hub

  3. Activate it without restarting:

    /reload-plugins

Overview

Meeting-to-Action Agent

Turns messy meeting transcripts and rough notes into clean, structured deliverables — decision logs, action registers, and stakeholder follow-up drafts — then pushes tasks and records directly to Jira and Confluence (or Azure DevOps Boards). Designed for RBA delivery managers, project managers, account leads, and architects who live in back-to-back client meetings and need to close the loop fast.

What's in the bundle

Artifact What it does
meeting-transcript-parse skill Ingests raw transcripts (Teams, Zoom, manual notes, or paste) and produces a clean, normalized meeting record: participants, agenda items covered, discussion points, decisions made, and unresolved questions
decision-log-builder skill Extracts and formats decisions from a parsed meeting record into a structured decision log entry (DACI-style: Driver, Approver, Contributor, Informed) — ready to paste into Confluence or append to a project register
action-item-tracker skill Pulls every action item from a meeting record, assigns an owner and due date, validates against named participants, and outputs a formatted action register in markdown and/or CSV
meeting-followup-draft skill Drafts a polished stakeholder follow-up email or Teams message: re-states decisions, lists actions with owners and deadlines, flags unresolved items, and matches RBA's professional but direct communication style
jira-confluence-push skill Takes the structured action register and/or decision log and pushes them to Jira (create/update issues) and Confluence (append to meeting notes page) via the Atlassian MCP server or REST API
meeting-action-reviewer agent Sub-agent that does an independent review of a parsed meeting record before any push — checks owner coverage, missing due dates, vague action language, and unresolved decisions
/meeting command Entry-point slash command: accepts a transcript or notes file and routes to the full parse → review → push pipeline

When to use

  • You come out of a client status call, sprint review, or steering committee with a recording or rough notes and need clean minutes + action items in under 15 minutes
  • You want to stop Jira tickets from falling through the post-meeting gap — every action item gets a ticket, every ticket gets an owner
  • You're a DM or PM on a Sitecore, Optimizely, or Umbraco implementation and decisions need to land in the project Confluence space, not just in someone's inbox
  • You need a follow-up email that matches RBA's professional tone without spending 30 minutes drafting it
  • Your client is internal (RBA leadership or cross-discipline team) or external (client stakeholders, vendor partners)

Platform adapter note

Skills are platform-agnostic by default. The jira-confluence-push skill detects your environment (Jira Cloud, Jira Data Center, Azure DevOps Boards) and adapts the push mechanism accordingly. Decision log formatting includes a DACI template (Atlassian-style) with an optional RACI variant for teams that prefer that model.

How to install

claude plugin install meeting-to-action@rba-ai-hub

After install, the five skills, the reviewer agent, and the /meeting command are available immediately.

Permissions required

Skills in this bundle use:

  • Read — to ingest transcript files you point at
  • Write — to produce action register and decision log files locally
  • WebFetch(domain:api.atlassian.com) — for Jira and Confluence Cloud REST API pushes
  • WebFetch(domain:dev.azure.com) — for Azure DevOps Boards integration (optional adapter)

No credentials are stored by the skills. You supply your Atlassian API token or Azure PAT via environment variable (ATLASSIAN_API_TOKEN, ATLASSIAN_BASE_URL, AZURE_DEVOPS_PAT) before the push skill runs.

Composing with other plugins

  • discovery-synthesizer — after a discovery workshop, parse the transcript here first, then feed themes into discovery-interview-synthesis
  • business-analysis — action items from requirements workshops feed directly into epic decomposition
  • estimate-sow-builder — decisions made in scoping calls can be logged here and referenced when drafting the SOW

Bundled artifacts

Skills

  • action-item-tracker — Extracts every action item from a normalized meeting record or raw notes block, assigns owners and due dates, validates against named participants, and outputs a complete action register in markdown table and optional CSV format. Apply when the user asks to "pull the action items," "who owns what," "build the action register," or "track the follow-ups from this meeting." Also applies when reviewing whether prior meeting actions are complete before writing a follow-up. Skip when the user wants to push actions to Jira directly — chain to jira-confluence-push after this skill.
  • decision-log-builder — Extracts decisions from a normalized meeting record (from meeting-transcript-parse) or a raw notes block and formats them as structured decision log entries using a DACI model (Driver, Approver, Contributor, Informed). Outputs entries ready to append to a Confluence project decision log or a standalone markdown register. Apply when the user asks to "build the decision log," "log the decisions from this meeting," "add to the decision register," or "document what was decided." Also applies when a steering committee or governance meeting produced explicit decisions that need to be permanently recorded. Skip when no decisions were made — use action-item-tracker for meetings that are purely task-oriented.
  • jira-confluence-push — Pushes structured action items and decision log entries to Jira (create/update issues) and Confluence (append to a meeting notes page or decision register) via the Atlassian MCP server or REST API. Also supports Azure DevOps Boards as an alternative work-item backend. Apply when the user asks to "push to Jira," "create the tickets," "update Confluence," "log the decisions in Confluence," or "sync the action register." Requires ATLASSIAN_API_TOKEN and ATLASSIAN_BASE_URL environment variables (or AZURE_DEVOPS_PAT for ADO). Skip when the user only wants a local markdown output — use action-item-tracker or decision-log-builder for that.
  • meeting-followup-draft — Drafts a polished stakeholder follow-up email or Microsoft Teams message from a normalized meeting record and/or action register. Restates decisions, lists assigned actions with owners and deadlines, flags unresolved questions, and matches RBA's professional but direct communication style. Apply when the user asks to "draft the follow-up," "write the meeting email," "send the summary," or "post the recap to Teams." Works for both internal and client-facing follow-ups. Skip when the user wants to push to Confluence instead of email — use jira-confluence-push for that.
  • meeting-transcript-parse — Ingests a raw meeting transcript or rough notes — from Microsoft Teams, Zoom, a recording auto-caption export, or manual copy-paste — and produces a clean, normalized meeting record with participants, agenda items covered, discussion threads, decisions, action items, unresolved questions, and parking-lot items. Apply when the user pastes or references a transcript, notes file, or meeting recording export and asks to "clean up," "summarize," "pull actions from," or "write up" a meeting. Works for internal RBA team meetings, client status calls, steering committees, sprint reviews, and discovery workshops. Skip when the user already has a structured record and only wants to build a decision log (use decision-log-builder) or push to Jira (use jira-confluence-push).

Agents

  • meeting-action-reviewer — Independent sub-agent that reviews a normalized meeting record or action register before any push to Jira/Confluence. Checks for owner coverage gaps, missing due dates, vague action language, unresolved decisions, and completeness of the decision log. Surfaces findings as a prioritized checklist the user must clear (or explicitly acknowledge) before the follow-up email goes out or the Jira push runs. Invoke after meeting-transcript-parse and action-item-tracker, before meeting-followup-draft or jira-confluence-push.

Slash Commands

  • /meeting — Entry-point slash command for the meeting-to-action pipeline. Accepts a transcript, notes file, or pasted text and routes through the full workflow — parse → review → follow-up draft → optional Jira/Confluence push. Handles the full lifecycle in one command or lets the user step through stages interactively.
Technical details
Homepage
https://rba-skills.tylerschroeder.net/plugins/meeting-to-action/
License
MIT
Maturity
experimental
Security review
No security review
Owners
  • delivery
Disciplines
delivery, project-management
Lifecycle
communicate
Tags
  • meeting-notes
  • action-items
  • decision-log
  • jira
  • confluence
  • atlassian
  • transcript
  • follow-up
  • stakeholder-communication
  • minutes
  • mcp
  • azure-devops
Last updated
by Tyler Schroeder
Source
plugins/meeting-to-action/

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