/meeting
Paste into Claude Code, Claude.ai, the desktop app, or the browser extension — ⌘/Ctrl+V. ✓ Copied. Switch to Claude and paste — ⌘/Ctrl+V.
/meeting — Meeting-to-Action Pipeline
The single entry point for turning a raw meeting transcript or notes into a complete set of deliverables: clean meeting record, decision log, action register, follow-up draft, and optional Jira/Confluence push.
Usage
/meeting [transcript text or @file-path] [--stage all|parse|review|followup|push] [--type status-call|steering-committee|sprint-review|discovery|internal] [--audience internal|client|vendor] [--backend jira|ado] [--project <JIRA-KEY>] [--dry-run]
Arguments
| Argument | Default | Description |
|---|---|---|
transcript |
Required | Raw transcript, notes text, or @path/to/file.txt |
--stage |
all |
Run the full pipeline or stop at a specific stage |
--type |
Auto-detect | Meeting type — affects parsing rules and follow-up tone |
--audience |
client |
Who receives the follow-up — affects anonymization and tone |
--backend |
jira |
Work item system for the push stage |
--project |
Prompt if absent | Jira project key or ADO project name |
--dry-run |
Off | Preview Jira/Confluence push without executing |
Pipeline stages
When --stage all (default), the command runs this sequence:
1. meeting-transcript-parse — clean the raw input
2. meeting-action-reviewer — independent gap review
3. [pause] — present review findings; ask user to resolve P0s
4. action-item-tracker — finalize action register
5. decision-log-builder — format decision log entries
6. meeting-followup-draft — draft follow-up email/Teams message
7. [confirm] — ask user: push to Jira/Confluence? (yes/no/dry-run)
8. jira-confluence-push — create issues + update Confluence
The command pauses at step 3 (after the review) and step 7 (before the push) to let the user intervene. It does not push to Jira or Confluence without explicit confirmation.
Stage shortcuts
Run only part of the pipeline:
/meeting @notes.txt --stage parse # Step 1 only: produce normalized record
/meeting @record.md --stage review # Step 2 only: review an existing record
/meeting @record.md --stage followup # Steps 4–6: produce follow-up draft only
/meeting @register.md --stage push # Step 8 only: push an existing register
Quick start examples
After a client status call (paste transcript):
/meeting "Sarah: Thanks everyone for joining. Let's start with..." --type status-call --audience client
From a saved Teams transcript file:
/meeting @downloads/teams-transcript-2026-05-28.txt --type steering-committee --project ACM-SXC
Dry-run Jira push to preview what would be created:
/meeting @action-register.md --stage push --dry-run
Internal sprint review, push to Azure DevOps:
/meeting @sprint7-review.md --type sprint-review --audience internal --backend ado
What gets created
After a full pipeline run, you will have:
| Output | Format | Location |
|---|---|---|
| Normalized meeting record | .md |
./meeting-record-<YYYY-MM-DD>.md |
| Action register | .md + optional .csv |
./action-register-<YYYY-MM-DD>.md |
| Decision log entries | .md |
./decisions-<YYYY-MM-DD>.md |
| Follow-up draft | .md (copy-paste ready) |
Returned inline |
| Jira issues | Created in your project | Returned as issue key list |
| Confluence updates | Appended to your page | Returned as page URL |
Notes
- The pipeline never sends emails or posts to Teams directly — it drafts text for you to copy. Sending is always a manual step.
- Jira and Confluence pushes require
ATLASSIAN_API_TOKENandATLASSIAN_BASE_URLto be set. The command checks these before attempting the push and provides setup instructions if they are missing. - Use
--dry-runon any push stage to see exactly what would be created before committing.
Technical details
- Source
- meeting-to-action
- Author
- Dakota Smith
- Invocation
/meeting- Maturity
- experimental
- Security review
- No security review
- Owners
-
- delivery
- File
plugins/meeting-to-action/commands/meeting.md
Edit this command on GitHub — opens GitHub's web editor. No git knowledge needed.